From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Thu, 17 May 2012 21:14:16 -0500
Subject: [U-Boot] [PATCH 5/6] cmd_nvedit.c: allow board-specific code
 before/after saving the environment
In-Reply-To: <4FB58187.2040506@freescale.com>
References: <1336170092-22538-1-git-send-email-timur@freescale.com>
	<1336170092-22538-5-git-send-email-timur@freescale.com>
	<201205140120.45712.vapier@gentoo.org>
	<4FB12E88.1050906@freescale.com>
	<20120517221808.2AEAE206271@gemini.denx.de>
	<4FB58038.8060004@freescale.com> <4FB58187.2040506@freescale.com>
Message-ID: <4FB5B078.4050000@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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