[U-Boot] [PATCH 5/6] cmd_nvedit.c: allow board-specific code before/after saving the environment

Scott Wood
2012-05-18T02:14:16Z

On 05/17/2012 05:53 PM, Timur Tabi wrote:
> Scott Wood wrote:
>> NAND doesn't need it because NAND goes through an API rather than direct
>> memory-mapped access, and has more coarse-grained operations. NAND
>> should be able to take care of this entirely in the driver using the
>> select_chip() callback.
>
> Fair enough. How do I enable that feature? Do I create my own
> board_nand_init() and then do this:
>
> this->select_chip = p1022ds_nand_select_chip;

board_nand_init() is implemented in drivers/mtd/nand/fsl_elbc_nand.c.
You'll need to add some board hook there.

>> Timur, is there any reason to use NOR rather than NAND with this chip?
>
> Well, as with most of our boards, NOR is the default configuration. Also,
> there's no NAND support upstream yet.

What isn't upstream, besides the muxing hack? Does it need the 4K page
hack?

-Scott