From: "H. Peter Anvin" <hpa@transmeta.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
Device List Maintainer <device@lanana.org>
Subject: Re: Minors remaining in Major 10 ??
Date: Sat, 20 Jan 2001 21:40:09 -0800 [thread overview]
Message-ID: <3A6A7639.7F4A0A21@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101201651070.657-100000@master.linux-ide.org>
Andre Hedrick wrote:
>
> Hi Peter,
>
> Regardless if we rip out the entire rule of majors for dev_t, will there
> be a service dummy driver to various block-devices? There is a real need
> for this if we are going to get full control of the hardware by indirect
> access obtain the functionality that I see and need in the near future.
>
At this point, I'll allocate a device number when someone is ready to
release a driver - no sooner. There simply is not a whole lot of choice
because of the extreme shortage of device numbers that's going to last us
until dev_t gets expanded.
-hpad
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-21 5:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A6A28B2.83807A1@transmeta.com>
2001-01-21 5:36 ` Minors remaining in Major 10 ?? Andre Hedrick
2001-01-21 5:40 ` H. Peter Anvin [this message]
2001-01-21 5:44 ` Andre Hedrick
2001-01-20 8:45 Andre Hedrick
2001-01-20 22:13 ` H. Peter Anvin
2001-01-20 23:06 ` Andre Hedrick
2001-01-20 23:12 ` H. Peter Anvin
2001-01-20 23:40 ` Andre Hedrick
2001-01-21 0:42 ` Jens Axboe
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=3A6A7639.7F4A0A21@transmeta.com \
--to=hpa@transmeta.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=device@lanana.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox