JustAnother wrote:Presumably the extra HDaudio IDs will be of use to someone.
Those "new HDAudio PCI device IDs" could be very useful for me, if they would fix old bugs in the notorious "generic driver" oss_hdaudio
In general Azalia based systems (laptops/motherboards) would require a custom driver
to work properly. Due to enormous number of different systems it is not possible to develop such custom drivers for all systems. A generic driver
is used for systems that don't have dedicated drivers
However codecs are different. To make things even worse motherboard manufacturers have complete freedom to decide which I/O pin they connect the jacks and other audio inputs and outputs. It is not enough to write just one mixer driver for each codec. This needs to be done by hand for every single motherboard (unless there are boards that have the pins assigned in the same way).
The mixgen.c can be used to create a skeleton of a mixer driver. Then the result can be fine tuned by using trial and error approach. http://permalink.gmane.org/gmane.comp.a ... devel/1155
Notice that ALSA has similar problems https://help.ubuntu.com/community/HdaIntelSoundHowto
The users of the "very advanced open-source crap" are invited to file bug reportshttps://wiki.ubuntu.com/DebuggingSoundProblemshttps://help.ubuntu.com/community/ReportingBugs/http://linuxhaters.blogspot.de/2008/08/ ... m-all.html
The "closed source" version of OSS4 must be upgraded urgently, because the old licence expired. Otherwise, Ubuntu users may ask "very strange questions" on the forum, for example: viewtopic.php?f=3&t=4198
The "open source" version of OSS4 might be upgraded after summer holidays, or after Christmas.
In any case, we have to wait for the much desired "dedicated drivers" just like our brothers in Vanuatu are waiting for John Frum and his Cargo planes: http://www.youtube.com/watch?v=qmlYe2KS0-Y
The problem is that it is rather difficult (for OSS4 developers) to develop "custom drivers" for all existing notebooks http://manuals.opensound.com/usersguide/hdaudio.html
Perhaps, the most obvious solution is to teach ordinary users how to make own drivers. What is needed is a comprehensive manual, a kind of step-by-step tutorial.
A simple toolkit with a manual for dummies might be a magic solution to all problems. It may unleash creativity, out-of-the-box thinking
, and innovation. It may remove social barriers between "stupid users" and "arrogant developers" and create an atmosphere where participants will feel involved and valuable, because their input will make a difference. A lot of Russian kids (not to mention audiophiles) might be happy to have such a Lego
for making audio drivers.
In our day, if you want to survive on the market, you have to provide tools with which ordinary users can create own drivers, or own applications. What the users really need is to solve their problems. They need a kind of Lego
for making own toys. Example: Android SDK
In essence, OSS4 is a Stone Age technology. The users have to wait for years until the developers provide "dedicated" audio drivers for notebooks, which may soon be out of use. If OSS4 cannot respond to the technological challenges of 21st century, it has to be consigned to the dustbin of history