MMC block major dev

From: Pierre Ossman (drzeus-list_at_drzeus.cx)
Date: 08/31/04

  • Next message: Martin J. Bligh: "Re: CONFIG_ACPI totally broken (2.6.9-rc1-mm2)" 
    Date:	Tue, 31 Aug 2004 21:13:52 +0200
To: Russell King <rmk+lkml@arm.linux.org.uk>, linux-kernel@vger.kernel.org

    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.

    Some debug statements revealed that the driver ended up on major number
    254. I'm not familiar with how kernel memory is initialized but using an
    uninitialized variable should result in random numbers. It seems to get
    254 each time though. Can I count on this? (i.e. can I safely create
    device node files with this major).

    Rgds
    Pierre Ossman

    -
    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/

  • Next message: Martin J. Bligh: "Re: CONFIG_ACPI totally broken (2.6.9-rc1-mm2)"