From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?= Date: Wed, 27 Feb 2013 14:40:51 +0100 (CET) Subject: [U-Boot] [PATCH v2 2/2] mtd: nand: mxc_nand: Fix is_16bit_nand() In-Reply-To: <20130227141521.2e0d8ca4@e6520eb> References: <1361903720-26935-1-git-send-email-fabio.estevam@freescale.com> <1361903720-26935-2-git-send-email-fabio.estevam@freescale.com> <20130227121104.15c16b00@e6520eb> <1701948647.144167.1361969590454.JavaMail.root@advansee.com> <20130227141521.2e0d8ca4@e6520eb> Message-ID: <893687444.145237.1361972451573.JavaMail.root@advansee.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Eric, On Wednesday, February 27, 2013 2:15:21 PM, Eric B?nard wrote: > Hi Beno?t, > > Le Wed, 27 Feb 2013 13:53:10 +0100 (CET), > Beno?t Th?baudeau a ?crit : > > > > This code is not used for NAND boot, for which the SPL version of this > > driver > > and CONFIG_SYS_NAND_BUSWIDTH_16 are used. > > > I didn't follow SPL migration (I have to come back to it so the next > question may be stupid sorry in advance) but once u-boot is running > isn't it using the "standard" driver and no more the SPL one ? Yes, that's correct (unless you need to access NAND only from SPL). But if any board booting from NAND had a 16-bit NAND, CONFIG_SYS_NAND_BUSWIDTH_16 would have to be defined, which no board does, so none of these boards needs CONFIG_SYS_NAND_BUSWIDTH_16BIT either. And the rest of the explanation is what Fabio has just said. Best regards, Beno?t