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

[Timur Tabi]

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;

> 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.

-- 
Timur Tabi
Linux kernel developer at Freescale