From: Greg Lindahl <greg.lindahl@qlogic.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: ak@suse.de, olson@unixfolk.com, discuss@x86-64.org,
brice@myri.com, linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
Date: Tue, 20 Jun 2006 13:41:09 -0700 [thread overview]
Message-ID: <20060620204109.GA1980@greglaptop.internal.keyresearch.com> (raw)
In-Reply-To: <20060620132049.ff5e6f67.rdunlap@xenotime.net>
On Tue, Jun 20, 2006 at 01:20:49PM -0700, Randy.Dunlap wrote:
> Does it cover the 10 new models that are available tomorrow?
> (hypothetical question)
I see several people on this list who are aware of forthcoming PCI
Express server products, and they aren't objecting to broad
whitelisting of PCI Express.
Is there any known case of PCI Express and MSI not working on any
chipset? Andi, is the tg3 NIC that didn't work in a Supermicro system
on PCI-X or PCI Express?
-- greg
next prev parent reply other threads:[~2006-06-20 20:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.5FgZbVFZIyOdjQ3utdNvbqTrUq0@ifi.uio.no>
[not found] ` <fa.URgTUhhO9H/aLp98XyIN2gzSppk@ifi.uio.no>
2006-06-20 5:42 ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Dave Olson
2006-06-20 7:25 ` Andi Kleen
2006-06-20 8:02 ` Jeff Garzik
2006-06-20 8:13 ` Andi Kleen
2006-06-20 8:27 ` Jeff Garzik
2006-06-20 22:44 ` Eric W. Biederman
2006-06-20 20:03 ` Greg Lindahl
2006-06-20 20:20 ` Randy.Dunlap
2006-06-20 20:26 ` Brice Goglin
2006-06-20 20:41 ` Greg Lindahl [this message]
2006-06-20 20:50 ` Brice Goglin
2006-06-20 20:53 ` Jeff Garzik
2006-06-20 20:57 ` Dave Olson
2006-06-20 20:23 ` Roland Dreier
2006-06-20 20:54 ` Jeff Garzik
2006-06-20 21:29 ` Greg KH
2006-06-20 22:27 ` Brice Goglin
2006-06-20 23:05 ` Greg KH
2006-06-20 23:16 ` Brice Goglin
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
2006-06-17 3:01 [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Brice Goglin
2006-06-17 14:48 ` Brice Goglin
[not found] ` <20060619005329.GA1425@greglaptop>
2006-06-19 8:28 ` [discuss] " Andi Kleen
2006-06-19 12:52 ` Brice Goglin
2006-06-19 15:47 ` Greg Lindahl
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=20060620204109.GA1980@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=linux-kernel@vger.kernel.org \
--cc=olson@unixfolk.com \
--cc=rdunlap@xenotime.net \
/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