From: Adrian Bunk <bunk@kernel.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
rmk@arm.linux.org.uk, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [4/5] update the BLK_DEV_HD help text
Date: Wed, 25 Jun 2008 00:55:34 +0300 [thread overview]
Message-ID: <20080624215533.GF18252@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <200806221521.33506.bzolnier@gmail.com>
Many people will see this option the first time now that it is in
drivers/block/
Make it clear that virtually noone needs it.
Signed-off-by: Adrian Bunk <bunk@kernel.org>
---
drivers/block/Kconfig | 26 +++++++-------------------
1 file changed, 7 insertions(+), 19 deletions(-)
6071700205968d31a74a695a678188f2cbcf0eb8 diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index c9ab7ef..46eb920 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -434,27 +434,15 @@ config VIRTIO_BLK
lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
config BLK_DEV_HD
- bool "Old hard disk (MFM/RLL/IDE) driver"
+ bool "Very old hard disk (MFM/RLL/IDE) driver"
depends on HAVE_IDE
depends on !ARM || ARCH_RPC || ARCH_SHARK || BROKEN
help
- There are two drivers for MFM/RLL/IDE hard disks. Most people use
- the newer enhanced driver, but this old one is still around for two
- reasons. Some older systems have strange timing problems and seem to
- work only with the old driver (which itself does not work with some
- newer systems). The other reason is that the old driver is smaller,
- since it lacks the enhanced functionality of the new one. This makes
- it a good choice for systems with very tight memory restrictions, or
- for systems with only older MFM/RLL/ESDI drives. Choosing the old
- driver can save 13 KB or so of kernel memory.
-
- If you want to use this driver together with the new one you have
- to use "hda=noprobe hdb=noprobe" kernel parameters to prevent the new
- driver from probing the primary interface.
-
- If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
- instead of this one. For more detailed information, read the
- Disk-HOWTO, available from
- <http://www.tldp.org/docs.html#howto>.
+ This is a very old hard disk driver that lacks the enhanced
+ functionality of the newer ones.
+
+ It is required for systems with ancient MFM/RLL/ESDI drives.
+
+ If unsure, say N.
endif # BLK_DEV
next prev parent reply other threads:[~2008-06-24 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 22:21 [2.6 patch] fix BLK_DEV_HD_ONLY on ARM dependencies Adrian Bunk
2008-06-10 17:56 ` Bartlomiej Zolnierkiewicz
2008-06-22 10:17 ` Adrian Bunk
2008-06-22 13:21 ` Bartlomiej Zolnierkiewicz
2008-06-24 21:54 ` [0/5] move hd.c to drivers/block/ Adrian Bunk
2008-06-25 20:16 ` Bartlomiej Zolnierkiewicz
2008-06-24 21:54 ` [1/5] remove BLK_DEV_HD_ONLY Adrian Bunk
2008-06-24 21:54 ` [2/5] ide/legacy/hd.c: use late_initcall() Adrian Bunk
2008-06-24 21:54 ` [3/5] move ide/legacy/hd.c to drivers/block/ Adrian Bunk
2008-06-24 21:55 ` Adrian Bunk [this message]
2008-06-24 22:05 ` [5/5] hd.c: remove the #include <linux/mc146818rtc.h> Adrian Bunk
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=20080624215533.GF18252@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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®