From: "David S. Miller" <davem@davemloft.net>
To: Jeff Garzik <jgarzik@pobox.com>
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 15:40:30 -0800 [thread overview]
Message-ID: <20050322154030.310e85c1.davem@davemloft.net> (raw)
In-Reply-To: <42409BA4.3090302@pobox.com>
On Tue, 22 Mar 2005 17:26:44 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> I disagree: this will hide bugs.
It actually spots them too. :-) If you'd like it to print out
something like:
TG3 MSI test failed on chipset ven[%x] devid[%x] please
email this info to PCI maintainers at x@y.com
that's fine.
> We already have a standard process in Linux to handle this stuff:
>
> * avoid platform tests in the driver
> * when the driver fails, have the user try "pci=nomsi"
> * if that works, add system to blacklist
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.
next prev parent reply other threads:[~2005-03-22 23:40 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 [this message]
2005-03-22 23:50 ` Jeff Garzik
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=20050322154030.310e85c1.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).