From: Greg Lindahl <greg.lindahl@qlogic.com>
To: Andi Kleen <ak@suse.de>
Cc: Jeff Garzik <jeff@garzik.org>, Dave Olson <olson@unixfolk.com>,
Brice Goglin <brice@myri.com>,
linux-kernel@vger.kernel.org, gregkh@suse.de, discuss@x86-64.org
Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ
Date: Wed, 21 Jun 2006 18:32:22 -0700 [thread overview]
Message-ID: <20060622013222.GF2614@greglaptop.internal.keyresearch.com> (raw)
In-Reply-To: <20060622012339.GD2614@greglaptop.internal.keyresearch.com>
On Wed, Jun 21, 2006 at 06:37:30PM +0200, Andi Kleen wrote:
> Because I don't think normal Linux users should be in the hardware validation
> business. If the vendor says it's not tested we shouldn't enable it by default.
All you're going to do is piss off all the distros and hardare vendors
shipping systems with this chip in it. Nvidia is not the only "vendor"
involved, and is not the only one doing hardware validation. Sun, HP,
Newisys, and LNXI all have currently shipping Opteron products with a
CK804. All 4 are probably going to want your employer's distro to not
disable MSI.
-- greg
next prev parent reply other threads:[~2006-06-22 1:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 4:42 [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ Allen Martin
2006-06-21 10:05 ` Andi Kleen
2006-06-21 16:21 ` Dave Olson
2006-06-21 16:37 ` Andi Kleen
[not found] ` <20060622012339.GD2614@greglaptop.internal.keyresearch.com>
2006-06-22 1:32 ` Greg Lindahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-23 15:43 Naren (Narendra) Sankar
[not found] <fa.5FgZbVFZIyOdjQ3utdNvbqTrUq0@ifi.uio.no>
2006-06-20 7:25 ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Andi Kleen
2006-06-20 21:29 ` Greg KH
2006-06-20 22:33 ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ Andi Kleen
2006-06-20 22:46 ` Roland Dreier
2006-06-21 6:19 ` Dave Olson
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=20060622013222.GF2614@greglaptop.internal.keyresearch.com \
--to=greg.lindahl@qlogic.com \
--cc=ak@suse.de \
--cc=brice@myri.com \
--cc=discuss@x86-64.org \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olson@unixfolk.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