[cdi-devel] Proposed Sound Infrastructure
Kevin Wolf ·
On Mon, Nov 23, 2009 at 12:10:47PM +1000, Matthew Iselin wrote: > Right, and I think a method to access other devices from CDI drivers > would be rather handy at times as well. This should be another CDI > "system call", in my opinion. How that call looks is probably > something to be discussed - it needs to be generic for driver code but > at the same time able to cater to many different ways for an OS to > handle devices. Any ideas? We found that getting this IDC (Inter Driver Communication) part right is the most important thing for now, so I'm ignoring the whole audio stuff for now. I have tried to write down some header file fragments that would make up a suitable framework, both for monolithic kernels and microkernel systems. Basically the only new thing is the abstraction of memory areas that allows a (microkernel) OS to use shared memory for the actual sound data, so that the user application can create the buffer and it doesn't need to be copied anywhere. Other OSes might decide not to implement this but rather do a copy. Monolithic kernels will probably just pass pointers around. I'm attaching a first attempt of the header. Comments are appreciated. Kevin -------------- next part -------------- A non-text attachment was scrubbed... Name: ipc.c Type: text/x-c++src Size: 1597 bytes Desc: not available URL: <http://list.tyndur.org/pipermail/cdi-devel/attachments/20091123/690ca70e/attachment.c>