On Wednesday 01 October 2008, Roman Mashak wrote: > > Flash ID is in $(UBOOT)/include/linux/mtd/nand_ids.h > > Seems this chip is not CFI compliant (at least datasheet says nothing > > of it), so the use of CFI driver falls away. > > After some investigations I see that $(uboot)/drivers/mtd/nand/nand.c > is compiled in with CONFIG_CMD_NAND defined and CFG_NAND_LEGACY > undefined -- these two macros are mutually exclusive.
Correct. The legacy NAND support is, as the name implies, outdated and should *not* be used anymore. > Why do then some > platforms define both of them, for instance > $(uboot)/include/configs/at91rm9200dk.h and what is the proper use of > these macros? Defining both is definitely broken and should be fixed. I think now its really time to completely remove the legacy NAND support. It has been dragged along for quite some time. > To make things more clear: NAND flash Samsung K9F1G08U is defined in > both $(uboot)/drivers/mtd/nand/nand_ids.c and > $(uboot)/include/linux/mtd/nand_ids.h, latter is included with > CFG_NAND_LEGACY defined. It confuses me, I don't understand is my > flash legacy device or rather new one? :-) IIRC then your NAND chips should be supported in the U-Boot NAND driver without any changes. Best regards, Stefan ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: [EMAIL PROTECTED] ===================================================================== _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
