> >> Actually, I'm not completely opposed to the idea. But I am totally >> clueless when it comes to writing device drivers, and would have no >> idea where to start. > >Start here: http://www.alsa-project.org/documentation.php3#Driver > >You don't have to start writing the driver from scratch. You only >have to fix the current driver so you can also select 96KHz from >the PCM interface. The API is not difficult to learn.
there's almost no API work to do. the problem is really simple and already solved in a closely related driver. when you change between an SS (44.1/48) and DS rate (88.2/96), it changes the channel count. this would be a bad thing if the PCM device is open, because it alters all the addresses of the channel buffers etc. etc. so the driver prevents you from doing this if the PCM device is open. this creates a paradox, because you've already got the device open. the hdsp driver takes a different approach to this, even though it faces an identical problem. its a better design, one based on our experience with the digi9652 driver and its shortcomings. i'd love to go in and fix the digi9652, but short of some compelling reason for me to do so, with the work on ardour+jack at the level it is right now, i just don't have time. >> Do you know if RME were forthcoming with specs? > >I asked for infos one year ago, but they just said no. they don't want to get involved with lots of people being sent specs. the driver itself is the best source of documentation - its more accurate than the information they sent me :) --p ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
