Re: [microblaze-uclinux] Source of kernel boot message, "MBVanillaflash probe..."?

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi David,

David Banas wrote:

>>>instead of using a constant from the new "auto-config" flow?
>>
>>Basically I had to ensure I didn't break any old (ie mbvanilla) targets.
>>  You should see in that same directory a file ml401_flash.c (or
>>similar).  It uses the auto-config parameters as you would expect.

> So, where does the choice get made regarding which "*-flash.c" file to
> compile?

Check out the Makefile in that directory, you'll find a bunch of lines 
that look like this:

obj-$(CONFIG_MTD_XXX_XXX) += xxxxxxxx.o

If a particular MTD config option (e.g. CONFIG_MTD_MBVANILLA) is set to 
'y', then the necessary object file will be added to the list of objects 
to be build (obj-y).  Then the Makefule implicit rules will know to 
compile xxxxx.c to build xxxxx.o

This mechanism is used throughout the entire 2.4 kernel.

Regards,

John


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/