From: Jeff Dike <jdike@addtoit.com>
To: akpm@osdl.org
Cc: Allan Graves <allan.graves@gmail.com>,
linux-kernel@vger.kernel.org,
user-mode-linux@lists.sourceforge.net
Subject: [PATCH 1/3] UML - Enable RAW
Date: Tue, 20 Feb 2007 11:56:37 -0500 [thread overview]
Message-ID: <20070220165636.GA6246@ccure.user-mode-linux.org> (raw)
From: Allan Graves <allan.graves@gmail.com>
Date: Fri Jan 26 17:49:00 2007
[PATCH] Enable raw.ko in UML
- This patch adds the RAW device driver options to the UML
Kconfig.char file so that you may use them in UML.
Signed-off-by: Allan Graves<allan.graves@gmail.com>
Signed-off-by: Jeff Dike <jdike@addtoit.com>
--
arch/um/Kconfig.char | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
Index: linux-2.6.18-mm/arch/um/Kconfig.char
===================================================================
--- linux-2.6.18-mm.orig/arch/um/Kconfig.char 2007-01-17 06:02:47.000000000 -0500
+++ linux-2.6.18-mm/arch/um/Kconfig.char 2007-01-23 11:29:06.000000000 -0500
@@ -146,6 +146,25 @@ config LEGACY_PTYS
security. This option enables these legacy devices; on most
systems, it is safe to say N.
+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 will be removed soon.
+ 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 LEGACY_PTY_COUNT
int "Maximum number of legacy PTY in use"
--
Work email - jdike at linux dot intel dot com
reply other threads:[~2007-02-20 17:04 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=20070220165636.GA6246@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=allan.graves@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux@lists.sourceforge.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 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.