RE: updated dma to user space API

[<And...@no...>]

> > Sebastien Rougeaux wrote:
> > The important part for me
> > is that the driver:
> > 
> >     . allows multi-buffering (tunable)
> >     . doesn't waste CPU time
> >     . does frame synchronization

> 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.

I also think that interpretations of iso packets should be left to the
application. The 1394 driver should only address 1394 related issues, not
application specific stuff such as reception of isochronous DV streams. DV
is the most important usage for isochronous transfers today but we will most
likely see a lot of new things in the future. The best thing to do, I think,
is to keep the driver as clean as possible and conentrate on having it up to
date with the development of 1394.


Keep up the good work everyone!


Regards,
Anders Weitman