Linked by nfeske on Thu 28th Feb 2013 12:08 UTC
Thread beginning with comment 554015
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
We haven't used existing code for the new audio interface. Low-level interfaces like this one are tightly coupled to the Genode API. Reusing existing work would have meant to create a glue layer between the existing code (that is typically expecting a POSIX-like environment, using mmap, Unix-domain sockets etc.) and the Genode API. I am afraid that this glue layer alone would have exceeded our custom implementation in terms of code complexity.
That said, nothing is set in stone. If we see, down the road, that adopting an existing solution would have been a better choice, we can still revise our decision. To come to the right judgement, we need to gather experience with the new interface first.




Member since:
2005-07-06
About the 'low latency output': I seem to remember similar design in CoreAudio and/or PulseAudio (can't remember), did you use code from these project or did you invent your own way?