Can PYSMAP_COMPAT go?

[Wolfram Sang]

> And this was i386, which unfortunately doesn't use the device-tree yet,
> although on these embedded SoC devices it really _should_ be doing so.
> And it doesn't have 'platform code' either.

Okay, so unless i386 gets device-tree support ;), how about at least this?

From: Wolfram Sang <w.sang at pengutronix.de>
Subject: [PATCH] mtd/physmap: Use sensible default value for MTD_PHYSMAP_LEN

Commit 73566edf9b91dd085ddb12033d0ea7288979dd10 made it necessary to be
0, but commit dcb3e137ce9be1dfc86e306182b23e3ae5e239c4 obsoleted that
requirement. Restore the old value to get a meaningful default.

Signed-off-by: Wolfram Sang <w.sang at pengutronix.de>
---
 drivers/mtd/maps/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/mtd/maps/Kconfig b/drivers/mtd/maps/Kconfig
index aa2807d..213c615 100644
--- a/drivers/mtd/maps/Kconfig
+++ b/drivers/mtd/maps/Kconfig
@@ -47,7 +47,7 @@ config MTD_PHYSMAP_START
 config MTD_PHYSMAP_LEN
 	hex "Physical length of flash mapping"
 	depends on MTD_PHYSMAP_COMPAT
-	default "0"
+	default "0x4000000"
 	help
 	  This is the total length of the mapping of the flash chips on
 	  your particular board. If there is space, or aliases, in the
-- 
1.7.0


-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20100420/ad273594/attachment.sig>