From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Russell King <rmk+lkml@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: MMC block major dev
Date: Tue, 31 Aug 2004 21:47:59 +0200 [thread overview]
Message-ID: <4134D5EF.9080903@drzeus.cx> (raw)
In-Reply-To: <20040831201556.B11053@flint.arm.linux.org.uk>
Russell King wrote:
>On Tue, Aug 31, 2004 at 09:13:52PM +0200, Pierre Ossman wrote:
>
>
>>It seems that the MMC block layer hasn't been assigned a major number.
>>The code registers the block dev with a uninitialized variable. It then
>>proceeds to create a mmc dir under devfs. Since I'm not using devfs this
>>then poses a problem.
>>
>>
>
>First, "uninitialised variables" is a misdescription here. Variables
>declared outside the scope of functions are _always_ initialised even
>though there is no apparant assignment.
>
>They're placed in the BSS, or "zero initialised" section. They have
>a well defined value. Zero.
>
>Registering with the block layer with a major number of zero means
>"find me a free major number and assign that to me." This is nothing
>new. If devfs can't cope with that, devfs is buggy. Use udev instead.
>
>
>
Ok. Please excuse my ignorance =)
My point was that I do not use a dynamic system for /dev so it would be
nice to have a static major number. Since MMC now is a part of Linus'
kernel maybe it's time for a permanent allocation?
Rgds
Pierre
next prev parent reply other threads:[~2004-09-01 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:13 MMC block major dev Pierre Ossman
2004-08-31 19:15 ` Russell King
2004-08-31 19:47 ` Pierre Ossman [this message]
2004-09-01 12:16 ` Alan Cox
2004-09-01 21:55 ` Russell King
2004-09-01 21:28 ` Alan Cox
2004-09-01 12:18 ` Alan Cox
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=4134D5EF.9080903@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@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