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