From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lunge.queued.net ([173.255.254.236]) by canuck.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1REiq2-0006AV-Ui for linux-mtd@lists.infradead.org; Fri, 14 Oct 2011 14:34:19 +0000 Date: Fri, 14 Oct 2011 07:33:20 -0700 From: Andres Salomon To: David Woodhouse Subject: [PATCH v2] mtd: provide an alias for the redboot module name Message-ID: <20111014073320.140fb4b2@debxo> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, Artem Bityutskiy List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , parse_mtd_partitions takes a list of partition types; if the driver isn't loaded, it attempts to load it, and then it grabs the partition parser. For redboot, the module name is "redboot.ko", while the parser name is "RedBoot". Since modprobe is case-sensitive, attempting to modprobe "RedBoot" will never work. I suspect the embedded systems that make use of redboot just always manually loaded redboot prior to loading their specific nand chip drivers (or statically compiled it in). Signed-off-by: Andres Salomon Cc: stable@kernel.org --- drivers/mtd/redboot.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) v2: instead of renaming the module, use a module_alias. Duh. Thanks, Artem Bityutskiy! diff --git a/drivers/mtd/redboot.c b/drivers/mtd/redboot.c index 7a87d07..4938bd0 100644 --- a/drivers/mtd/redboot.c +++ b/drivers/mtd/redboot.c @@ -297,6 +297,9 @@ static struct mtd_part_parser redboot_parser = { .name = "RedBoot", }; +/* mtd parsers will request the module by parser name */ +MODULE_ALIAS("RedBoot"); + static int __init redboot_parser_init(void) { return register_mtd_parser(&redboot_parser); -- 1.7.2.5