Re: kmdf: Accessing data by isochronous transfer with 1394 device
- From: "min" <min@xxxxxx>
- Date: Thu, 20 Dec 2007 13:55:21 +0100
I really thank you for your advices :-)
Could you please explain a little bit more precisely about page boundary?
Did you mean page boundary of physical or logical memory?
Should I use common buffer to start all buffers on a page boundary?
What kind of differences are there between starting buffers on a page
boundary
and not on a page boundary?
Sorry for many questions...
regards,
min
"Matt Gonzalez" <matt@xxxxxxxxxxxxx> schrieb im Newsbeitrag
news:OktLL0mQIHA.5400@xxxxxxxxxxxxxxxxxxxxxxx
min wrote:
I'm using kmdf 1394 sample driver on WDK 6000It also seems to work better if your isochronous buffers all start on a
and I'm trying to access the transffered data in isochronous listen. (I
would like to take the transffered data and write it in a text file.)
Can somebody give me some advice or tips?
How (and when) can (or schould) I access the data? Has someone a example?
My idea is that I take the buffer in 't1394_IsochCallback' function,
because when DMA is completed to a buffer, it will call Callback
function.
page boundary.
.
- Follow-Ups:
- Re: kmdf: Accessing data by isochronous transfer with 1394 device
- From: Matt Gonzalez
- Re: kmdf: Accessing data by isochronous transfer with 1394 device
- References:
- Prev by Date: Support on a Power management problem
- Next by Date: COM_PowerUp & COM_PowerDown APIs
- Previous by thread: Re: kmdf: Accessing data by isochronous transfer with 1394 device
- Next by thread: Re: kmdf: Accessing data by isochronous transfer with 1394 device
- Index(es):
Relevant Pages
|