All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: mchan@broadcom.com, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6.11 4/8] tg3: Add msi test
Date: Tue, 22 Mar 2005 18:50:36 -0500	[thread overview]
Message-ID: <4240AF4C.9030109@pobox.com> (raw)
In-Reply-To: <20050322154030.310e85c1.davem@davemloft.net>

David S. Miller wrote:
> Just because it's what we've been doing doesn't mean it's the
> best solution in this case.
> 
> If you hope users will just report this stuff, most of them won't.
> They'll say Linux doesn't work on my computer and I have real life
> stuff to take care of so I'll install freebsd or windows or a different
> networking card and get on with life.
> 
> Eventually, say over a year or so, the database of bad chipsets will
> get built with your scheme, but to much hardship and pain to users.


What do you think will happen for all the other MSI drivers/hardware out 
there?

Adding this test to tg3 simply means another piece of hardware doesn't 
work.  The problem disappears for -you-, but not the user.

You're just pushing the pain around, for the -few- -early- systems with 
problems.

Sorry, I still disagree.  We need to think about how to handle this 
situation for -all- drivers and -all- users, not just tg3.

	Jeff

  reply	other threads:[~2005-03-22 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-22 22:07 [PATCH 2.6.11 4/8] tg3: Add msi test Michael Chan
2005-03-22 22:14 ` Jeff Garzik
2005-03-22 22:17   ` David S. Miller
2005-03-22 22:26     ` Jeff Garzik
2005-03-22 23:40       ` David S. Miller
2005-03-22 23:50         ` Jeff Garzik [this message]
2005-03-22 23:52           ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2005-03-23 18:16 Michael Chan
2005-03-21  7:43 Michael Chan
2005-03-22 20:57 ` Jeff Garzik

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=4240AF4C.9030109@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=davem@davemloft.net \
    --cc=mchan@broadcom.com \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.