[wdmaudiodev] Re: 32 bit structs ?
- From: "Cheng-mean Liu (SOCCER)" <soccerl@xxxxxxxxxxxxx>
- To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Tue, 14 Feb 2012 17:08:04 +0000
Those 32-bit versions of KS related structures were added for KS's thunking
purpose (between 32-bit apps on x64 bit Windows).
They are internal to KS and has no impact to apps or drivers. (They should have
been moved to non-public header.) Sorry for the confusion.
Thanks
Cheng-mean
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Bielik
Sent: Tuesday, February 14, 2012 8:20 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: 32 bit structs ?
Hi Matthew,
Matthew van Eerde skrev 2012-02-14 17:05:
> I can't think of a reason why anyone would use these.
Hmm... then why are they present in the SDK ? :)
Can't it be something to do with running a 32 bit application on 64 bit Windows
f.i. ? Or something similar ? Still, compiling a 32 bit application would mean
that PVOID is 32 bit, which would make it equal to the *****32 variant, so that
shouldn't be it either...
Regards,
/Rob
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx
> [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Bielik
> Sent: Monday, February 13, 2012 9:43 PM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] 32 bit structs ?
>
> Ooops, I just encountered several dually defined structs for communicating
> with WaveRT device drivers:
>
> KSRTAUDIO_BUFFER_PROPERTY vs. KSRTAUDIO_BUFFER_PROPERTY32
> KSRTAUDIO_BUFFER_PROPERTY_WITH_NOTIFICATION vs.
> KSRTAUDIO_BUFFER_PROPERTY_WITH_NOTIFICATION32
> ...
>
> and I am now worried that the failure to use the ******32 structs will be
> problematic sometimes (the implementation in question is the Portaudio WDM/KS
> implementation).
>
> Could someone knowledgeable line up where and why I should be using ******32
> structs instead of their counterpart ?
>
> TIA
> /Rob
>
>
> ******************
>
> WDMAUDIODEV addresses:
> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
> Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
> Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
>
> URL to WDMAUDIODEV page:
> http://www.wdmaudiodev.com/
>
>
>
> ******************
>
> WDMAUDIODEV addresses:
> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
> Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
> Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
>
> URL to WDMAUDIODEV page:
> http://www.wdmaudiodev.com/
>
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
Other related posts:
