All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] mtd: nand: mxc_nand: Fix is_16bit_nand()
Date: Wed, 27 Feb 2013 14:40:51 +0100 (CET)	[thread overview]
Message-ID: <893687444.145237.1361972451573.JavaMail.root@advansee.com> (raw)
In-Reply-To: <20130227141521.2e0d8ca4@e6520eb>

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 <benoit.thebaudeau@advansee.com> 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

  reply	other threads:[~2013-02-27 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 18:35 [U-Boot] [PATCH v2 1/2] mtd: nand: Introduce CONFIG_SYS_NAND_BUSWIDTH_16BIT Fabio Estevam
2013-02-26 18:35 ` [U-Boot] [PATCH v2 2/2] mtd: nand: mxc_nand: Fix is_16bit_nand() Fabio Estevam
2013-02-26 18:47   ` Benoît Thébaudeau
2013-02-26 19:11     ` Fabio Estevam
2013-02-27 11:11   ` Eric Bénard
2013-02-27 12:53     ` Benoît Thébaudeau
2013-02-27 13:15       ` Eric Bénard
2013-02-27 13:40         ` Benoît Thébaudeau [this message]
2013-02-27 17:18           ` Eric Bénard
2013-02-27 13:16     ` Fabio Estevam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=893687444.145237.1361972451573.JavaMail.root@advansee.com \
    --to=benoit.thebaudeau@advansee.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.