[less intrusive PATCH, RFC] don't load physmap if length is zero

Mark Brown broonie at sirena.org.uk
Mon Mar 13 13:47:30 EST 2006


On Sun, Mar 12, 2006 at 11:12:48PM +0100, J?rn Engel wrote:
> On Tue, 28 February 2006 20:16:42 +0100, Lennert Buytenhek wrote:

> > I'd still prefer the platform driver patch to be applied, but having
> > some kind of solution merged is better than no solution at all :-)

> Is there a good reason why you didn't just write your own mapping
> driver?  Most people copy physmap.c, change a few things and use that
> driver instead of physmap.c.  It does involve many copies of
> essentially the same code, but that code is very simple and no sane
> kernel should have more than one mapping driver included, so no object
> code is duplicated.

It is reasonable to have multiple board variants with differing flash
setups but still want them all to run the same kernel.  If you're using
platform devices to tell the world about the rest of the differing fit
information it's reasonable to also want to use it for the flash.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."




More information about the linux-mtd mailing list