Preferred way to configure MTD physical mapping and partitioning

[David Woodhouse]

On Mon, 2006-05-22 at 12:32 +0200, Laurent Pinchart wrote:
> - adding a board specific "driver" in drivers/mtd/maps and handle all mapping 
> manually
> - adding board specific MTD configuration in arch/ppc/platforms with calls to 
> physmap_set_partitions() and physmap_configure()
> - adding board specific MTD configuration in arch/ppc/platforms with a call to 
> physmap_set_partitions(), and using the CONFIG_MTD_PHYSMAP option with 
> physical mapping values provided in the kernel configuration.
> 
> Could anyone comment on the preferred approach ?

None of the above. The physmap driver in the MTD git tree already works
with a platform_device, instead of needing a call to physmap_configure()
or manual configuration at build time. Either register a
platform_device, or preferably extend it to use an of_device too.

-- 
dwmw2