From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, zippel@linux-m68k.org
Cc: Joel.Becker@oracle.com, akpm@digeo.com,
andrey@eccentric.mae.cornell.edu, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: major/minor split
Date: Thu, 20 Mar 2003 23:24:33 +0100 (MET) [thread overview]
Message-ID: <UTC200303202224.h2KMOXC01107.aeb@smtp.cwi.nl> (raw)
> There is a point I'd like to get clear: where should the
> 16bit<->32bit dev_t conversion happen?
I am not sure I understand the question, but if I do
the answer is "nowhere", there is no conversion
(other than the lengthening that happens when one
casts an unsigned short to an unsigned int).
For dev_t (8,1) is 0x00000801, but (8,256) is 0x00080100.
(In case of a 16+16 split. Not that I advocate that,
it is just easy talking.)
For kdev_t (8,1) is 0x00080001 and (8,256) is 0x00080100.
So kdev_t allows simple fast composition and decomposition,
but is restricted to the kernel.
While dev_t requires a conditional, since it has to remain
compatible with the old 8+8 userspace.
> how can software create nodes for a specific device?
You do not mean using mknod?
Andries
next reply other threads:[~2003-03-20 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 22:24 Andries.Brouwer [this message]
2003-03-20 23:23 ` Roman Zippel
2003-03-21 0:04 ` H. Peter Anvin
2003-03-20 23:52 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 7:35 Andries.Brouwer
2003-03-19 21:40 Andries.Brouwer
2003-03-20 21:00 ` Roman Zippel
2003-03-20 21:47 ` Joel Becker
2003-03-20 22:03 ` Joel Becker
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=UTC200303202224.h2KMOXC01107.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=Joel.Becker@oracle.com \
--cc=akpm@digeo.com \
--cc=andrey@eccentric.mae.cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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®