Mapping for JEDEC and CFI

[Fabrice Gautier <gautier@email.enst.fr>]

Hi,

I think there is a problem in Config.in wrt CFI and JEDEC custom
mapping.

What's the differnece between CONFIG_MTD_PHYSMAP:

   dep_tristate '  CFI Flash device in physical memory map' CONFIG_MTD_PHYSMAP $CONFIG_MTD_CFI
   if [ "$CONFIG_MTD_PHYSMAP" = "y" -o "$CONFIG_MTD_PHYSMAP" = "m" ]; then
      hex '    Physical start address of flash mapping' CONFIG_MTD_PHYSMAP_START 0x8000000
      hex '    Physical length of flash mapping' CONFIG_MTD_PHYSMAP_LEN 0x4000000
      int '    Bus width in octets' CONFIG_MTD_PHYSMAP_BUSWIDTH 2
   fi

and  CONFIG_MTD_CSTM_CFI_JEDEC:

   dep_tristate '  CFI and JEDEC Flash device mapping on custom board' CONFIG_MTD_CSTM_CFI_JEDEC $CONFIG_MTD_CFI
   if [ "$CONFIG_MTD_CSTM_CFI_JEDEC" = "y" -o "$CONFIG_MTD_CSTM_CFI_JEDEC" = "m" ]; then
      hex '    Physical start address of flash mapping' CONFIG_MTD_PHYSMAP_START 0x8000000
      hex '    Physical length of flash mapping' CONFIG_MTD_PHYSMAP_LEN 0x4000000
      int '    Bus width in octets' CONFIG_MTD_PHYSMAP_BUSWIDTH 2
      define_bool CONFIG_MTD_JEDEC y
   fi


And by the way, why the support for custom JEDEC mapping is here and not
with the JEDEC driver?

Thanks
-- 
Fabrice Gautier <gautier@email.enstfr>



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org