On Tuesday 24 January 2006 06:47, Sergei Steshenko wrote: >On Tue, 24 Jan 2006 12:42:32 +0100 > >Takashi Iwai <[EMAIL PROTECTED]> wrote: >> At Tue, 24 Jan 2006 13:03:45 +0200, >> >> Sergei Steshenko wrote: >> > P.S. On Mandriva 2006.0 'xpdf' is broken. So, being constructively >> > lazy, I just replaced it with the one from Mandriva 10.2. Of >> > course, I did this by picking Mandriva 10.2 'xpdf' RPM. That is, I >> > reverted to older BINARY version. >> > >> > I believe that ALSA users should have the ability to simply revert >> > to older binary version of ALSA as well. >> >> The binary compatibility of alsa-lib has been kept for long time. >> We have occasionally fixes and extensions, but the old binary should >> run. >> >> However, the often problematic part during versions is the >> confiugration. It's not API/ABI. >> >> >> Takashi > >Again, in simple English, is there a document describing how >to install, say, binary ALSA version 1.0.6 on 2.6.15 kernel ?
I don't know about the document, but up until a week ago, I had been running alsalib-1.0.3b with kernels as new as 2.6.16-rc1. My hardware hadn't changed until I added an SB Audigy2 Value card in all this time, so why should the userland driver change? >Also, please see very recent Lee's note and pay attention to these > words: > >" >This won't work as 1.0.9-rc4 is older than the version that comes with >kernel 2.6.13. Either use the latest ALSA release (1.0.10) or just > use the version included with kernel 2.6.13. >". > > >Guys, actually, nobody cares how you call it - ABI or API. > >Let's talk in consumer's language - if newer binary version doesn't >work, but an older binary version used to work, making the whole thing >work should be no more complex than replacing new 'xpdf' RPM with the >old one. Agreed. [...] This whole thread is essentially a waste of time, and somewhat resembles elephant breeding in that there is a lot of trumpeting and foot stomping, and it will be 22 months before the results can be known to be successfull. What we preach here has very close to zero effect either on the kernel people, or on the vendor whose code is tied up in so much cross licenseing of patents and copyrights that there is no way in hell it will be released because if he did, the lawyers will have them for lunch, as the main course. It _is_ how things are, either get used to it or go bug the proprietary people & leave us alone. The only way the situation will ever change is if and when linux becomes more than 5% of that vendors bottom line. At that point, market forces alone will fix the problem, or that vendor will become irrevelant, maybe even extinct by the time linux has hit the 10% mark. We, for all our high and mighty sounding debates, can do nothing about it that takes effect _today_. This thread is a waste of everyones time. Lets end it and get back to business as usual, which I'm told, on this list, has to do with alsasound support. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
