From: Olaf Hering <olh@suse.de>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com
Subject: [PATCH] add raw driver Kconfig entry for s390
Date: Sat, 13 May 2006 13:52:56 +0200 [thread overview]
Message-ID: <20060513115255.GA11955@suse.de> (raw)
From: Ihno Krumreich <ihno@suse.de>
The raw module is not enabled on s390/s390x
During SLES9 and SLES10 development IBM filed bugs about the missing raw
driver. Avoid that for SLES11 by adding it to the other char driver
entries.
Signed-off-by: Olaf Hering <olh@suse.de>
---
drivers/s390/Kconfig | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
Index: linux-2.6.16/drivers/s390/Kconfig
===================================================================
--- linux-2.6.16.orig/drivers/s390/Kconfig
+++ linux-2.6.16/drivers/s390/Kconfig
@@ -51,6 +51,26 @@ config UNIX98_PTY_COUNT
When not in use, each additional set of 256 PTYs occupy
approximately 8 KB of kernel memory on 32-bit architectures.
+config RAW_DRIVER
+ tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
+ help
+ The raw driver permits block devices to be bound to /dev/raw/rawN.
+ Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
+ See the raw(8) manpage for more details.
+
+ The raw driver is deprecated and may be removed from 2.7
+ kernels. Applications should simply open the device (eg /dev/hda1)
+ with the O_DIRECT flag.
+
+config MAX_RAW_DEVS
+ int "Maximum number of RAW devices to support (1-8192)"
+ depends on RAW_DRIVER
+ default "256"
+ help
+ The maximum number of RAW devices that are supported.
+ Default is 256. Increase this number in case you need lots of
+ raw devices.
+
config HANGCHECK_TIMER
tristate "Hangcheck timer"
help
next reply other threads:[~2006-05-13 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 11:52 Olaf Hering [this message]
2006-05-13 12:12 ` [PATCH] add raw driver Kconfig entry for s390 Christoph Hellwig
2006-05-15 8:30 ` Martin Schwidefsky
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=20060513115255.GA11955@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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.