Messages in this thread | | | Date | Tue, 31 Aug 2004 20:15:56 +0100 | From | Russell King <> | Subject | Re: MMC block major dev |
| |
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.
-- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |