Re: updated dma to user space API
Brought to you by:
aeb,
bencollins
From: Sebastien R. <Seb...@sy...> - 2000-05-11 04:46:13
|
>>>>> "Anders" == Anders Weitman <And...@no...> writes: >> Manfred Weihs wrote: I do not aggree with you. That should not be done by >> the driver; any interpretation of the content of an iso packet should be >> done by the application. The driver shall deliver the raw packets (as >> libraw does now) and the application should decide, what the data is and >> whether it has to look for sync tags and things like that. Anders> I also think that interpretations of iso packets should be left to the Anders> application. The 1394 driver should only address 1394 related issues, Anders> not application specific stuff such as reception of isochronous DV Anders> streams. DV is the most important usage for isochronous transfers Anders> today but we will most likely see a lot of new things in the Anders> future. The best thing to do, I think, is to keep the driver as clean Anders> as possible and conentrate on having it up to date with the Anders> development of 1394. What I had in mind is a frame grabber driver... of course we can think of a more low-level iso receive driver (in fact just removing the sync tag in my current iso receive driver would probably work for more general iso reception). -- Sebastien Rougeaux RSISE, The Australian National University |