diff options
| author | Andres Salomon <dilinger@queued.net> | 2011-10-14 07:33:20 -0700 |
|---|---|---|
| committer | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2011-10-16 14:56:33 +0300 |
| commit | d5de1907d0af22e1a02de2b16a624148517a39c2 (patch) | |
| tree | 6ac7e707824e32a19716890f21c1f9eaf2f68d86 /drivers/mtd | |
| parent | 5f949137952020214cd167093dd7be448f21c079 (diff) | |
| download | op-kernel-dev-d5de1907d0af22e1a02de2b16a624148517a39c2.zip op-kernel-dev-d5de1907d0af22e1a02de2b16a624148517a39c2.tar.gz | |
mtd: provide an alias for the redboot module name
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>
Cc: stable@kernel.org
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 56e48ea..f40ba86 100644 --- a/drivers/mtd/redboot.c +++ b/drivers/mtd/redboot.c @@ -296,6 +296,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); |
