From: Greg Stark <gsstark@mit.edu>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Greg Stark <gsstark@mit.edu>,
linux-kernel@vger.kernel.org,
Patrick McFarland <pmcfarland@downeast.net>
Subject: Re: OSS Audio borked between 2.6.6 and 2.6.10
Date: 13 Mar 2005 22:50:00 -0500 [thread overview]
Message-ID: <87sm2y7uon.fsf@stark.xeocode.com> (raw)
In-Reply-To: <200503140103.55354.s0348365@sms.ed.ac.uk>
Alistair John Strachan <s0348365@sms.ed.ac.uk> writes:
> The intel8x0 driver is probably one of the most widely used ALSA drivers, so
> I'd hope it wasn't broken!
I would have hoped so too at the time. Reporting it to the list didn't get any
response since it was already fixed upstream, but it took a while before it
was merged down to the linux tree.
Also, it seems chipsets can be wired up differently in different motherboards.
A driver can work perfectly for hundreds of boards and still fail on the same
chipset on another machine.
In any case "X code is broken" "why not use Y code instead" isn't really
productive. It's a good thing I was using the OSS drivers; if everyone used
the alsa drivers and nobody was testing the OSS drivers nobody would know they
were broken.
--
greg
next prev parent reply other threads:[~2005-03-14 3:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 18:31 OSS Audio borked between 2.6.6 and 2.6.10 Greg Stark
2005-03-13 6:52 ` Patrick McFarland
2005-03-13 22:26 ` Greg Stark
2005-03-14 0:48 ` Martin Schlemmer
2005-03-14 1:03 ` Alistair John Strachan
2005-03-14 3:50 ` Greg Stark [this message]
2005-03-14 4:07 ` Andrew Morton
2005-03-14 4:42 ` Greg Stark
2005-03-14 4:55 ` Andrew Morton
2005-03-14 5:39 ` Greg Stark
2005-03-14 5:57 ` Andrew Morton
2005-03-14 6:21 ` Greg Stark
2005-03-14 6:48 ` Andrew Morton
2005-03-14 8:59 ` Greg Stark
2005-03-14 9:53 ` Andrew Morton
2005-03-14 15:40 ` Greg Stark
2005-03-14 15:52 ` John W. Linville
2005-03-22 0:38 ` Andrew Morton
2005-03-22 4:16 ` Greg Stark
2005-03-14 15:33 ` John W. Linville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sm2y7uon.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pmcfarland@downeast.net \
--cc=s0348365@sms.ed.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox