* Confused about audio drivers - where do I start? @ 2007-03-22 23:01 Timur Tabi 2007-03-22 23:22 ` Randy Dunlap 2007-03-22 23:32 ` Andreas Mohr 0 siblings, 2 replies; 3+ messages in thread From: Timur Tabi @ 2007-03-22 23:01 UTC (permalink / raw) To: linux-kernel If I were to write a non-USB audio device driver from scratch (for new hardware), what interface would I use? Has ALSA become the official Linux kernel audio subsystem? Is there a specific device driver I should use as a sample? -- Timur Tabi Linux Kernel Developer @ Freescale ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Confused about audio drivers - where do I start? 2007-03-22 23:01 Confused about audio drivers - where do I start? Timur Tabi @ 2007-03-22 23:22 ` Randy Dunlap 2007-03-22 23:32 ` Andreas Mohr 1 sibling, 0 replies; 3+ messages in thread From: Randy Dunlap @ 2007-03-22 23:22 UTC (permalink / raw) To: Timur Tabi; +Cc: linux-kernel On Thu, 22 Mar 2007 18:01:01 -0500 Timur Tabi wrote: > If I were to write a non-USB audio device driver from scratch (for new hardware), what > interface would I use? Has ALSA become the official Linux kernel audio subsystem? Is Yes. > there a specific device driver I should use as a sample? Dunno. But ALSA has docs. See http://www.alsa-project.org/documentation.php#0.9doc --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Confused about audio drivers - where do I start? 2007-03-22 23:01 Confused about audio drivers - where do I start? Timur Tabi 2007-03-22 23:22 ` Randy Dunlap @ 2007-03-22 23:32 ` Andreas Mohr 1 sibling, 0 replies; 3+ messages in thread From: Andreas Mohr @ 2007-03-22 23:32 UTC (permalink / raw) To: Timur Tabi; +Cc: linux-kernel Hi, On Thu, Mar 22, 2007 at 06:01:01PM -0500, Timur Tabi wrote: > If I were to write a non-USB audio device driver from scratch (for new > hardware), what interface would I use? Has ALSA become the official Linux > kernel audio subsystem? Is there a specific device driver I should use as > a sample? Yes, a driver should definitely be written against ALSA. It's probably a good idea to use the most wide-spread card/driver close to the hardware/functionality area of your new card as a sample driver, the reasoning being that due to that card's wide use it's most likely that all features are implemented as expected there. And make sure to examine your new hardware about which sound card standards it supports (AC-97, ...) which already have good generic support in ALSA. When designing the mixer interface, definitely read ControlNames.txt and name all mixer controls properly, since mixer apps have strongly differing behaviour and may not work correctly without very strict and verbose control naming. This implies wide testing with different mixer apps, too (gamix, alsamixer, alsamixergui, gnome-alsamixer, kmix, aumix, ...). Why I'm saying this? Because the first user report about my azt3328 driver let me realize that some controls' naming was still broken despite having fixed most of those a while ago... Andreas Mohr ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-03-22 23:32 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-03-22 23:01 Confused about audio drivers - where do I start? Timur Tabi 2007-03-22 23:22 ` Randy Dunlap 2007-03-22 23:32 ` Andreas Mohr
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox