On Monday 04 September 2006 10:31, Takashi Iwai wrote: >At Mon, 04 Sep 2006 07:15:54 -0400, > >Gene Heskett wrote: >> On Monday 04 September 2006 06:46, Takashi Iwai wrote: >> >At Mon, 4 Sep 2006 13:32:27 +0300, >> > >> >Sergei Steshenko wrote: >> >> On Mon, 4 Sep 2006 18:25:10 +0800 >> >> >> >> "littertiger" <[EMAIL PROTECTED]> wrote: >> >> > hi, group >> >> > How to develop and configure plugins? I find the document is too >> >> > brief. anyone cound suggest some materials,or book? >> >> > >> >> > Best Regards >> >> > littertiger >> >> > [EMAIL PROTECTED] >> >> > 2006-09-04 >> >> >> >> As I understand the situation, ALSA developers are fiercely opposed >> >> to writing end user documentation unless they are payed for this :-) >> >> . >> > >> >Well, more correctly, unless they give us time and guts for this. >> >(and irony won't give neither of them :-) >> >> I'm not sure if that was irony, Takashi. Besides, the word is "paid". > >That what I mentioned. Also, another correction: developers are not >"opposing" but less interested (in comparison with the demand from >end-users :-) > >> But, it seems to me that at some point the developers are going to be >> so buried in this that the only way to save your sanity is to write >> some docs that at least specify how its done for the rapidly >> proliferating chip selections that the chip people have succeeded in >> actually making a racket with that passes for sound in most circles. >> Without this, each developer will keep re-inventing the wheel. That >> doesn't appear to be the best way to spend your often valuable time. > >Well, in your argument it's not clear what level of documentation is >urgently needed.
Something along the lines of: chipset aaaa needs this in your modprobe.conf yadda yadda chipset aaab needs this in your modprobe.conf yadda yadda. Repeat till out of chipsets or hard drive to catalog them. The yadda yadda portion would look something like this: ---------- # sound stuff, subject to heavy mods in future # For Alsa # 1st, make the SB Live / SB Audigy 2 the default alias snd-card-0 snd-emu10k1 # 2nd, and then skype can use /dev/dsp1 alias snd-card-1 snd-intel8x0 # For Alsa's Oss emulation? alias snd-slot-0 snd-card-0 alias snd-slot-1 snd-card-1 # Alsa's Oss emulation # supposedly for emu10k1/SBLive Value/Audigy 2 Value stuff alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss # supposedly for nforce2's ac97 crap # But somethings fubar here yet. alias sound-service-1-0 snd-mixer-oss alias sound-service-1-1 snd-seq-oss alias sound-service-1-3 snd-pcm-oss alias sound-service-1-8 snd-seq-oss alias sound-service-1-12 snd-pcm-oss # But, whats this? alias char-major-116-* snd alias char-major-14-* sound install synth0 /bin/true alias snd-slot-2 off # end of sound ---------- snipped down to a format more like 'sound-service-#a-#b snd-mixer-oss' with an explanatory rule decreeing how to determine the #a and #b numerals as shown above for a 2 card system where skype uses the 2nd card exclusivley. And FWIW, that last alias above doesn't do any good, my logs are still full of squawks about it not being available. >Actually, the difficulty in writing a document for >end-users is to know what they don't/need to know -- or a definition >of "end-users". We may need a tecnical reference for the developers, >while we may need a guidebook for novice users, or Gospels for >ex-window users. My mother cannot use a video recorder unless someone >tells her how to use it. But it's bundled with a good technical >reference for all information. I'd be the first to admit there are varying levels of help needed, and like you, I don't see a quick and dirty, 100% foolproof method to catalog the users levels (or lack thereof) of expertise. Thats a bit like nailing jelly to a tree... But an actual, working, example line or lines for modprobe.conf, along with a lucid explanation of what the numbers in the otherwise similar lines do, will often "turn on the lights" and the user can then follow, if not to a perfect conclusion which the above isn't, but at least to arrive at a working setup, which the above does well at. Everything works except the logs are 25% bigger per week because of the perceived errors that are logged. Here is a stanza of that from yesterdays log. --------- Sep 3 13:38:30 coyote modprobe: FATAL: Error running install command for sound_slot_2 Sep 3 13:42:44 coyote last message repeated 2 times Sep 3 13:45:48 coyote last message repeated 8 times Sep 3 13:48:36 coyote last message repeated 6 times Sep 3 13:49:47 coyote last message repeated 8 times Sep 3 13:51:24 coyote last message repeated 4 times Sep 3 13:51:32 coyote last message repeated 2 times ---------- Humm, good to get it all on one page, I named snd-slot-2 in the alias, but its bitching about sound-slot-2 so I'll add that to /etc/modprobe.conf just for grins. >Maybe we should start from FAQ, then someone can compile it as a >real tutorial (if needed)... > > >Takashi -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Alsa-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alsa-user
