public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Canter <marcus@vfxcomputing.com>,
	Nish Aravamudan <nish.aravamudan@gmail.com>,
	Pierre Ossman <drzeus-list@drzeus.cx>,
	LKML <linux-kernel@vger.kernel.org>,
	alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: intel 8x0 went silent in 2.6.11
Date: Fri, 04 Mar 2005 13:02:27 -0500	[thread overview]
Message-ID: <1109959348.6442.3.camel@mindpipe> (raw)
In-Reply-To: <4227EE73.60803@pobox.com>

On Fri, 2005-03-04 at 00:13 -0500, Jeff Garzik wrote:
> Lee Revell wrote:
> > If you want to complain, complain to the hardware manufacturers, who
> > make devices where bit $foo means $bar in one hardware revision, and
> > $baz in the next, and don't give us sufficient documentation to sort out
> > the mess.
> 
> That's not terribly productive.
> 
> Life is what it is.  We deal with it.

That was actually my point.  I guess I could have been a bit clearer...

Anyone who works with drivers knows that hardware manufacturers will
always do things like this.  There is absolutely no point in complaining
about it, either to the vendor or on LKML.  The only fix is to file a
good bug report so it can be fixed.

Lee



  reply	other threads:[~2005-03-04 18:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 12:51 intel 8x0 went silent in 2.6.11 Pierre Ossman
2005-03-03 17:45 ` Nish Aravamudan
2005-03-03 18:46   ` Mark Canter
2005-03-03 18:52     ` [Alsa-devel] " Lee Revell
2005-03-03 19:06       ` Mark Canter
2005-03-03 19:09         ` Lee Revell
     [not found]           ` <Pine.LNX.4.62.0503031410450.19015@krusty.vfxcomputing.com>
2005-03-03 19:22             ` Lee Revell
     [not found]             ` <29495f1d050303114379ab96b5@mail.gmail.com>
2005-03-03 19:47               ` Lee Revell
2005-03-03 20:33           ` Mark Canter
2005-03-03 23:49             ` Andrew Morton
2005-03-04  0:37               ` Pierre Ossman
2005-03-04 21:16                 ` Pierre Ossman
2005-03-05 19:00                   ` Lee Revell
2005-03-07 20:13                     ` Pierre Ossman
2005-03-07 20:26                       ` Takashi Iwai
2005-03-07 13:50                   ` Takashi Iwai
2005-03-07 20:16                     ` Pierre Ossman
2005-03-07 20:21                       ` Takashi Iwai
2005-03-08  1:10                         ` Pierre Ossman
2005-03-08 11:53                           ` Takashi Iwai
2005-03-08 12:46                             ` Pierre Ossman
2005-03-09  1:53                             ` Mark Canter
2005-03-09  3:02                               ` Lee Revell
2005-03-04  2:50               ` Mark Canter
2005-03-04  5:13           ` Jeff Garzik
2005-03-04 18:02             ` Lee Revell [this message]
2005-03-03 19:42         ` Nish Aravamudan
2005-03-04 20:40       ` Bill Davidsen
2005-03-04 20:44         ` Lee Revell
2005-03-04 20:44         ` Mark Canter
2005-03-04  0:36   ` Pierre Ossman
2005-03-04 20:36   ` Bill Davidsen
2005-03-04 21:06     ` Lee Revell

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=1109959348.6442.3.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=drzeus-list@drzeus.cx \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus@vfxcomputing.com \
    --cc=nish.aravamudan@gmail.com \
    /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