From: Greg KH <greg@kroah.com>
To: marcelo.tosatti@cyclades.com
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [BK PATCH] PCI Express patches for 2.4.27-pre3
Date: Mon, 24 May 2004 14:02:27 -0700 [thread overview]
Message-ID: <20040524210227.GC5532@kroah.com> (raw)
In-Reply-To: <20040524210205.GB5532@kroah.com>
ChangeSet 1.1428, 2004/05/24 13:33:53-07:00, blujuice@us.ibm.com
[PATCH] PCI: PCI Express help in 2.4
Here is a patch for describing PCI access mode - help in 2.4.
This aligns the help with what is in 2.6.
Documentation/Configure.help | 13 +++++++------
1 files changed, 7 insertions(+), 6 deletions(-)
diff -Nru a/Documentation/Configure.help b/Documentation/Configure.help
--- a/Documentation/Configure.help Mon May 24 13:52:08 2004
+++ b/Documentation/Configure.help Mon May 24 13:52:08 2004
@@ -4236,12 +4236,13 @@
PCI-based systems don't have any BIOS at all. Linux can also try to
detect the PCI hardware directly without using the BIOS.
- With this option, you can specify how Linux should detect the PCI
- devices. If you choose "BIOS", the BIOS will be used, if you choose
- "Direct", the BIOS won't be used, and if you choose "Any", the
- kernel will try the direct access method and falls back to the BIOS
- if that doesn't work. If unsure, go with the default, which is
- "Any".
+ With this option, you can specify how Linux should detect the
+ PCI devices. If you choose "BIOS", the BIOS will be used,
+ if you choose "Direct", the BIOS won't be used, and if you
+ choose "MMConfig", then PCI Express MMCONFIG will be used.
+ If you choose "Any", the kernel will try MMCONFIG, then the
+ direct access method and falls back to the BIOS if that doesn't
+ work. If unsure, go with the default, which is "Any".
PCI device name database
CONFIG_PCI_NAMES
next prev parent reply other threads:[~2004-05-24 21:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 21:01 [BK PATCH] PCI Express patches for 2.4.27-pre3 Greg KH
2004-05-24 21:02 ` Greg KH
2004-05-24 21:02 ` Greg KH [this message]
2004-05-25 6:53 ` Arjan van de Ven
2004-05-25 8:00 ` Greg KH
2004-05-25 11:32 ` Matthew Wilcox
2004-05-25 12:54 ` Marcelo Tosatti
2004-05-25 13:01 ` Arjan van de Ven
2004-05-25 13:24 ` Matthew Wilcox
2004-05-25 14:41 ` Greg KH
2004-05-26 2:49 ` Jeff Garzik
2004-05-26 4:29 ` Greg KH
2004-05-25 14:40 ` Greg KH
2004-05-25 16:59 ` Marcelo Tosatti
2004-05-25 17:05 ` Greg KH
[not found] <1ZuS0-1b4-15@gated-at.bofh.it>
[not found] ` <1ZuS3-1b4-35@gated-at.bofh.it>
2004-05-24 22:21 ` Andi Kleen
2004-05-24 22:40 ` Greg KH
[not found] ` <1ZE52-8sy-15@gated-at.bofh.it>
[not found] ` <1ZFaF-10N-13@gated-at.bofh.it>
[not found] ` <1ZIrV-3xS-7@gated-at.bofh.it>
[not found] ` <1ZJHt-4At-33@gated-at.bofh.it>
2004-05-25 13:38 ` Andi Kleen
[not found] ` <1ZLpV-5YK-37@gated-at.bofh.it>
[not found] ` <1ZNBb-7QA-1@gated-at.bofh.it>
2004-05-25 17:14 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 6:29 Durairaj, Sundarapandian
2004-05-26 13:48 ` Matthew Wilcox
2004-05-26 17:03 ` Greg KH
2004-05-26 17:30 ` 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=20040524210227.GC5532@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=marcelo.tosatti@cyclades.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.