[EMAIL PROTECTED] wrote: > On Wed, 21 Jan 2004 06:26, Don Levey wrote; > > > This doesn't appear to be the case. Am I asking for the ALSA > > developers to obtain and test every sound boadr on the market, > > every chipset? Not at all. I wouldn't mind some sort of clear > > chart, as has been suggested, specifying just WHAT is *fully* > > supported/tested. Another section, "should work", would be nice, > > as well as a "don't hold your breath" section. > > Great. So, go help build or resurrect a site which will help users > co-ordinate their testing results for their hardware! >
Sure - I'd love to. Of course, I don't have the bandwidth to host a site like that, and I'm not really a web designer, but I'd like to help in that if possible. > > This should be a reasonable request - the developers should know > >against which hardware they test, what passes and what fails. The > > Hmm. Unfortunately the developers can only test on the one or two > pieces of hardware that they use. I don't think it's reasonable to > expect them to personally collaborate testing results from potentially > thousands of users. Maybe 20 users say "it works perfectly", when > what they mean is "stereo output at 44kHz is audible when connected to > the speaker out, I haven't exhaustively tested everything else". > How about publishing the tests that they DO run? If a developer is writing and testing using, say, a Turtle Beach Montego II, then tell us that this is the case. At the very least I would know that this boadr has a good chance of working for me. If you've got a specific motherboard with on-board sound, tell me. Or the chipset, or whatever. The ALSA project home page is a great place for this, and has a lot of information - and could have more. > >middle section, the best-guess list, would probably be the > >hardest. Oh, and as long as I'm dreaming, it would be nice to see > >a clear and simple explanation of how to tell what chipset is on > >your card, so that we can refer to that instead of the > >manufacturer's model number. > > As long as it's a PCI card, `lspci'. I usually then just google for > the device ID :) (`lspci -n' will not convert the ID to a name). > There isn't a 1<->1 correspondance between device IDs and chipsets, > but usually you'll find your answer from there. OK, that's a good place to start - thanks! I don't come into this knowing a whole heck of a lot, but I can learn. I just can't make that learning a full time job+; I've got 1.5 of those and a family (as, I'm sure, many others have too). -Don ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
