From: Andi Kleen <ak@suse.de>
To: Dave Olson <olson@unixfolk.com>
Cc: Allen Martin <AMartin@nvidia.com>,
discuss@x86-64.org, Brice Goglin <brice@myri.com>,
linux-kernel@vger.kernel.org,
Greg Lindahl <greg.lindahl@qlogic.com>
Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ
Date: Wed, 21 Jun 2006 18:37:30 +0200 [thread overview]
Message-ID: <200606211837.30056.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0606210920170.30013@osa.unixfolk.com>
On Wednesday 21 June 2006 18:21, Dave Olson wrote:
> On Wed, 21 Jun 2006, Andi Kleen wrote:
>
> | "Allen Martin" <AMartin@nvidia.com> writes:
> |
> | > >
> | > > NForce4 PCI Express is an unknown - we'll see how that works.
> | > >
> | >
> | > MSI is not officially supported on nForce4 and hasn't been fully tested.
> |
> | Ok thanks for the information. We should definitely disable it by default
> | then, maybe with an boot option so that the speed-over-stability crowd
> | can enable it (+ possibly an oops taint bit)
>
> Why disable it, when it's clearly working?
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.
-Andi
next prev parent reply other threads:[~2006-06-21 16:37 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 [this message]
[not found] ` <20060622012339.GD2614@greglaptop.internal.keyresearch.com>
2006-06-22 1:32 ` Greg Lindahl
-- 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=200606211837.30056.ak@suse.de \
--to=ak@suse.de \
--cc=AMartin@nvidia.com \
--cc=brice@myri.com \
--cc=discuss@x86-64.org \
--cc=greg.lindahl@qlogic.com \
--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 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.