On Tuesday 24 January 2006 07:50, Sergei Steshenko wrote: >On Tue, 24 Jan 2006 12:39:06 +0000 > >James Courtier-Dutton <[EMAIL PROTECTED]> wrote: >> Sergei Steshenko wrote: >> > Takashi, as end user I want to know nothing about alsa-lib and >> > kernel. >> > >> > I want to have a website with driver per card, i.e. I want to >> > perform only intellectualy primitive lookup operation: read the >> > file names in repository, find the file which matches my card name >> > and install it. >> > >> > Like with 'xpdf' - I see the program name (moral equivalent of my >> > card name) and version suffix. If the newest version doesn't work, >> > I revert to an older one. >> >> Sergei, >> >> What we have with Linux is better than what you want. >> You install the Linux kernel, and you have support for all sound >> cards already there. No need to go searching the net for some driver >> like one has to do in Windows. >> If it is not already in the Linux kernel, your sound card is >> unlikely to work in Linux at all. >> If you want support or a bug fix for some particular sound card, you >> then have to either wait for your distro to support it. (similar to >> waiting for the manufacture's web site to be updated with a new >> driver), or alternatively, compile the kernel and alsa from sources, >> and get the very latest bug fixes and features. >> >> If you think about it, the Linux way is actually a lot better than >> the method you are describing. >> >> James > >Well, Jaroslav wants this discussion to be over... > So let it...
>I compiled kernel on a number of occasions a number of years ago. >And it even worked. I do too, following Linus's releases, currently running 2.6.16-rc1. >However, the number of configuration options is scary, and thus the >chance to make a mistake. Which is precisely why you copy the .config from the older version and then do a make oldconfig, which sets the new options from the older ones. >So, replacing just one part of the system (a driver in question), and >replacing it with the one compiled by you, the professionals, seems to > me to be a much safer option. > >Basically, end user should not be forced to compile a driver. >Any honest developer should release his/her code only after sanity > checks, the first of them being compileability. So, after that first > sanity check the compiled driver already exists. I'm the end user, and I have no problems with that, with either the idea that I might have to do it, or in doing it if the documentation is current. I'd even write "and your point is?" but this thread should end. So beit. -- 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
