diff options
| author | Andres Salomon <dilinger@queued.net> | 2011-10-14 07:33:20 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-11-11 09:37:15 -0800 |
| commit | 1bd1046f37d0a9a76bbcd45284229edacb8d890d (patch) | |
| tree | 2a9bb94b10cb479f514a77915f14b357055aee25 /drivers/mtd | |
| parent | 5805ad8491edbc343a07de169f32ade07dcb3406 (diff) | |
| download | kernel_samsung_smdk4412-1bd1046f37d0a9a76bbcd45284229edacb8d890d.zip kernel_samsung_smdk4412-1bd1046f37d0a9a76bbcd45284229edacb8d890d.tar.gz kernel_samsung_smdk4412-1bd1046f37d0a9a76bbcd45284229edacb8d890d.tar.bz2 | |
mtd: provide an alias for the redboot module name
commit d5de1907d0af22e1a02de2b16a624148517a39c2 upstream.
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 <dilinger@queued.net>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/mtd')
| -rw-r--r-- | drivers/mtd/redboot.c | 3 |
1 files changed, 3 insertions, 0 deletions
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); |