On Monday 06 July 2009 01:10:58 Stefan Roese wrote:
On Sunday 05 July 2009 22:34:39 Wolfgang Denk wrote:
i dont mind creating a dedicated command like "fl" that would act like "sf" in terms of reading/writing/erasing, but it still must be able to leverage the CFI code which means using the weak GPIO accessor functions.
Sounds like a plan.
I kind of like the idea to create a new set of commands for accessing such board specific NOR FLASH (can be used on "normal" NOR FLASH as well). Perhaps we could make it "generic" in a way that it can be used for all kind of "MTD devices". How about this "mtd" commandset:
Select MTD NOR device #1 (2nd NOR device): => mtd device nor 1
Or via mtdparts/mtdids: => mtd device nor0
so both syntaxes would be available when mtdparts support is enabled, or would it be one or the other ? we would want to avoid ambiguity -- is "nor" referring to the nor flashes or is it referring to a partition named "nor".
what flash devices does mtdparts support now ? i'm not really familiar with it and the README and doc/ files doesnt seem to cover it.
i guess each flash type would parse the additional commands however it liked and so the mtd command would just act as a multiplexer at this point. the current spi flash "sf" command is pretty flexible -- you specify the spi chip select to select the device and you can specify other parameters dynamically (like frequency). so when folding it in, we'd have: => mtd device sf <cs> [speed] [mode]
common/cmd_mtd.c common/cmd_mtd_sf.c common/cmd_mtd_nor.c ... -mike