Trying to get MTD to do anything...

Jared Hulbert jaredeh at
Thu Jan 12 12:11:44 EST 2006

> I don't know - the driver itself is being registered, since the printk I
> have put in are outputting to the kernel boot console. I get no other
> messages from the MTD system AT ALL.
> I asked where I need to debug to find out what causes the probe to be called
> - i.e. the area of code that starts up the MTD system, as I don't know where
> to start debugging

This seems more clear to me now.  You have a a sandgate map driver. 
You know it is being executed because of the printk()s, but it does
not actually call the probing routines.

>(I'm not talking about the map driver itself, but the
> code that call the map driver).

I'm not sure I understand your reasoning here.  The map driver is
being called.  The probing routines should be called by the map driver
but are not.  You need to debug the map driver at this point.

> There's no point in debugging in the probe
> function as I know that isn't being called.


> I created a file in the maps directory, which is a copy of the mainstone map
> (mainstone-flash.c)with alteration to match the sandgate2 flash map. I
> stated this in my previous message. This contains the module which is
> registered, but doesn't appear to be probed. There may be a problem with me
> misunderstanding what you mean map file - do you mean my Sandgate equivalent
> of mainstone-flash.c or is there a different map file I need to be sorting
> out?

Yes, I mean the sandgate equivalent of mainstone-flash.c.

> If it isn't being called (i.e. the probe section) how do I ensure that it
> *is* called????

Fix the map driver.

> I hope I have answered you questions satisfactorily this time.

Sorry about the unfriendly tone of the previous email.  It did not
read as I had intended.   I started and stopped that email several
times, apparently each time I restarted I added a new dig about not
answering question, oops :)

More information about the linux-mtd mailing list