From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nand: add ID for Micron MT29F8G08A
Date: Thu, 27 Sep 2012 17:27:42 -0500 [thread overview]
Message-ID: <1348784862.18375.28@snotra> (raw)
In-Reply-To: <1348784363.1432.28.camel@tellur> (from dev@lynxeye.de on Thu Sep 27 17:19:23 2012)
On 09/27/2012 05:19:23 PM, Lucas Stach wrote:
> Am Donnerstag, den 27.09.2012, 17:13 -0500 schrieb Scott Wood:
> > On 09/27/2012 05:08:03 PM, Lucas Stach wrote:
> > > Am Donnerstag, den 27.09.2012, 16:53 -0500 schrieb Scott Wood:
> > > > On 09/27/2012 04:49:31 PM, Lucas Stach wrote:
> > > > > As found on the Colibri T20 engineering sample board.
> > > > >
> > > > > Signed-off-by: Lucas Stach <dev@lynxeye.de>
> > > > > ---
> > > > > drivers/mtd/nand/nand_ids.c | 1 +
> > > > > 1 Datei ge?ndert, 1 Zeile hinzugef?gt(+)
> > > > >
> > > > > diff --git a/drivers/mtd/nand/nand_ids.c
> > > b/drivers/mtd/nand/nand_ids.c
> > > > > index 3953549..ae300fe 100644
> > > > > --- a/drivers/mtd/nand/nand_ids.c
> > > > > +++ b/drivers/mtd/nand/nand_ids.c
> > > > > @@ -105,6 +105,7 @@ const struct nand_flash_dev
> nand_flash_ids[]
> > > = {
> > > > > {"NAND 512MiB 3,3V 16-bit", 0xCC, 0, 512, 0,
> LP_OPTIONS16},
> > > > >
> > > > > /* 8 Gigabit */
> > > > > + {"NAND 1GiB 3,3V 8-bit", 0x38, 0, 1024, 0,
> LP_OPTIONS},
> > > > > {"NAND 1GiB 1,8V 8-bit", 0xA3, 0, 1024, 0,
> LP_OPTIONS},
> > > > > {"NAND 1GiB 3,3V 8-bit", 0xD3, 0, 1024, 0,
> LP_OPTIONS},
> > > > > {"NAND 1GiB 1,8V 16-bit", 0xB3, 0, 1024, 0,
> LP_OPTIONS16},
> > > > > --
> > > > > 1.7.11.4
> > > >
> > > > Does this chip support ONFI? If so, we don't use the ID table.
> > > >
> > > I just rechecked, the datasheet claims the chip supports ONFI
> 2.0, but
> > > it does not get detected by the u-boot NAND code without the
> entry in
> > > the id table. CONFIG_SYS_NAND_ONFI_DETECTION is set.
> >
> > Could you debug it? Could there be a problem in the NAND controller
> > (or the driver)?
> >
> Haven't done much in tracking this down much further. Could quite
> possible be a bug in the Tegra nand driver, this driver isn't in tree
> for a long time and it seems no Tegra board so far tried using ONFI.
I don't see the Tegra READID code using column, which is a problem.
Hopefully this is a driver limitation and not hardware, unlike i.MX.
-Scott
next prev parent reply other threads:[~2012-09-27 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 21:49 [U-Boot] [PATCH] nand: add ID for Micron MT29F8G08A Lucas Stach
2012-09-27 21:53 ` Scott Wood
2012-09-27 22:08 ` Lucas Stach
2012-09-27 22:13 ` Scott Wood
2012-09-27 22:19 ` Lucas Stach
2012-09-27 22:27 ` Scott Wood [this message]
2012-09-28 15:20 ` Lucas Stach
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=1348784862.18375.28@snotra \
--to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox