mtd maps

mtd maps

[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.

Greg W

Re: mtd maps

[Mark A. Greer]

Greg Weeks wrote:

> 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

Re: mtd maps

[Matt Porter]

On Tue, Mar 15, 2005 at 11:44:00AM -0700, Mark A. Greer wrote:
> Greg Weeks wrote:
> 
> > 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...

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

Re: mtd maps

[Josh Boyer]

On Tue, 2005-03-15 at 13:32 -0700, Matt Porter wrote:
> On Tue, Mar 15, 2005 at 11:44:00AM -0700, Mark A. Greer wrote:
> > Greg Weeks wrote:
> > 
> > > 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...
> 
> 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

Re: mtd maps

[Jörn Engel]

On Tue, 15 March 2005 19:33:33 -0600, Josh Boyer wrote:
> 
> 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

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