From: "Tero Jänkä" <tesaja@utu.fi>
To: linux-kernel@vger.kernel.org
Subject: Generic PCI IDE Chipset Support in 2.4.21-rc6
Date: Thu, 29 May 2003 23:23:22 +0300 [thread overview]
Message-ID: <20030529202322.GA6441@tron.yok.utu.fi> (raw)
A possible bug here. At least a 'bug' in the documentation if nothing else.
In menuconfig there are the following two entries:
[*] PCI IDE chipset support
[ ] Generic PCI IDE Chipset Support (NEW)
The help (?) for "PCI IDE chipset support" in menuconfig shows:
CONFIG_BLK_DEV_IDEPCI:
Say Y here for PCI systems which use IDE drive(s).
This option helps the IDE driver to automatically detect and
configure all PCI-based IDE interfaces in your system.
However in Documentation/Configure.help it says about CONFIG_BLK_DEV_IDEPCI:
Generic PCI IDE chipset support
CONFIG_BLK_DEV_IDEPCI
Say Y here for PCI systems which use IDE drive(s).
This option helps the IDE driver to automatically detect and
configure all PCI-based IDE interfaces in your system.
Notice the first line, "Generic PCI IDE chipset support", and this was
supposed to be help for "PCI IDE chipset support" (at least if menuconfig is
to be trusted).
There is no help (?) available for "Generic PCI IDE Chipset Support" at all
in menuconfig. And no references to CONFIG_BLK_DEV_GENERIC in
Documentation/Configure.help.
What is the purpose of "Generic PCI IDE Chipset Support" (CONFIG_BLK_DEV_GENERIC)?
When should it be enabled and when not?
When upgrading from 2.4.20, CONFIG_BLK_DEV_GENERIC is disabled by default,
even though CONFIG_BLK_DEV_IDEPCI is enabled. Is this how it should be?
I'd appreciate if any responses are cc:ed to me, since I'm not in the lkml.
--
Tero Jänkä
reply other threads:[~2003-05-29 20:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030529202322.GA6441@tron.yok.utu.fi \
--to=tesaja@utu.fi \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®