Skip to contentSkip to conversation

mtd maps

DISCUSSION Greg Weeks 5 participants 5 messages Mar 15, 2005 – Mar 21, 2005

lore
Share & tools
lore

Greg Weeks

author
#0 lore raw

Are mtd maps still in drivers/mtd/maps or has that all moved to the platform code? I have an mtd map for the mpc8560ads but it's in mtd/maps.

Greg W

#1 lore raw
Quoted 1 line · Greg Weeks

Are mtd maps still in drivers/mtd/maps or has that all moved to the platform code? I have an mtd map for the mpc8560ads but it's in mtd/maps.

The mtd code has changed so that platform code can get at the routines to set up the maps from there. arch/ppc/platforms/katana.c has its mtd maps there and I recently posted a patch that moves it for the chestnut as well.

I think its a good idea to move them to the platform code since the mtd maps are platform specific anyway. Plus its one less place to add/edit a file. But that's just my $0.02...

Mark

#2 lore raw
Quoted 6 lines · Mark A. Greer
Quoted 2 lines · Greg Weeks

Are mtd maps still in drivers/mtd/maps or has that all moved to the platform code? I have an mtd map for the mpc8560ads but it's in mtd/maps.

Quoted 8 lines

The mtd code has changed so that platform code can get at the routines to set up the maps from there. arch/ppc/platforms/katana.c has its mtd maps there and I recently posted a patch that moves it for the chestnut as well.

I think its a good idea to move them to the platform code since the mtd maps are platform specific anyway. Plus its one less place to add/edit a file. But that's just my $0.02...

But keep in mind that this currently only applies in the case where you need to map chips of the same type. Some boards have multiple chip types and physmap doesn't yet support that.

-Matt

#3 lore raw
Quoted 12 lines · Matt Porter
Quoted 11 lines · Mark A. Greer
Quoted 2 lines · Greg Weeks

Are mtd maps still in drivers/mtd/maps or has that all moved to the platform code? I have an mtd map for the mpc8560ads but it's in mtd/maps.

The mtd code has changed so that platform code can get at the routines to set up the maps from there. arch/ppc/platforms/katana.c has its mtd maps there and I recently posted a patch that moves it for the chestnut as well.

Quoted 7 lines
Quoted 3 lines

I think its a good idea to move them to the platform code since the mtd maps are platform specific anyway. Plus its one less place to add/edit a file. But that's just my $0.02...

But keep in mind that this currently only applies in the case where you need to map chips of the same type. Some boards have multiple chip types and physmap doesn't yet support that.

There is a driver in MTD CVS now called mphysmap (untested I believe), that might be able to deal with that. Eventually.

josh

#4 lore raw
Quoted 3 lines · Josh Boyer

There is a driver in MTD CVS now called mphysmap (untested I believe), that might be able to deal with that. Eventually.

If someone has the need and a test machine with remote access, it could get done rather soon.

Jörn

Signature · 3 lines
Beware of bugs in the above code; I have only proved it correct, but
not tried it.
-- Donald Knuth