Trying to get MTD to do anything...

Jared Hulbert jaredeh at
Thu Jan 12 14:14:17 EST 2006

> In fact, all I know is the register function in the driver is being called -
> i.e. the function in
>         module_init(init_sandgate2)
> the init_sandgate2 function IS being called.
> This function simply does the following :
>         return driver_register(&sandgate2_flash_driver);
> and a printk in the function does display.
> I am not sure what there is to fix. The driver gets registered, but probe is
> never called. Its correctly added to the driver structure (in fact a direct
> copy from the mainstone variant, but with name changes to match sandgate2) -
> what else is there to debug?

This is very different than what I am expecting...
Actually there is no mainstone map in 2.6.10 look at the lubbock one
for reference.

If the map isn't doing the probe, then maybe it expects physmap stuff?
 I've always used the platform specfic map file, so I'm not going to
be any help with the physmap.  Also I don't think the phymap stuff is
optimized yet.

More information about the linux-mtd mailing list