From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] NAND Re: mtdparts fails with NAND >= 4GB - Second try
Date: Sat, 12 Feb 2011 04:06:00 -0800 [thread overview]
Message-ID: <201102120406.01194.Aaron.Williams@caviumnetworks.com> (raw)
In-Reply-To: <4D565C00.2060403@free.fr>
On Saturday, February 12, 2011 02:08:00 am Albert ARIBAUD wrote:
> Le 12/02/2011 09:54, Aaron Williams a ?crit :
> > Octeon ebb6300(ram)# mw.b 0x1f400000 0xf0
> > Octeon ebb6300(ram)# mw.b 0x1f400000 0xf0
> > Octeon ebb6300(ram)# mw.b 0x1f4000AA 0x98
> > Octeon ebb6300(ram)# md.b 0x1f400020 20
> > 1f400020: 51 51 52 52 59 59 02 02 00 00 40 40 00 00 00 00
> > QQRRYY....@@.... 1f400030: 00 00 00 00 00 00 27 27 36 36 00 00 00 00 07
> > 07 ......''66......
>
> This, according to the CFI spec, gives us the proof that the Spansion
> chip is a x16 device in x8 mode.
>
> Can you now please, based on the knowledge that the device is x16 in x8
> mode, go through the CFI detection sequence agin and determine which
> line exactly fails to work as expected?
>
> > -Aaron
>
> Amicalement,
I'll take a look at this next week. The problem with the current code is that
it detects the chip width of 8 but a port width of 16 which results in 16-bit
writes. This fails for obtaining the manufacturer ID.
-Aaron
prev parent reply other threads:[~2011-02-12 12:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 0:24 [U-Boot] mtdparts fails with NAND >= 4GB Aaron Williams
2011-01-28 1:06 ` Scott Wood
2011-01-28 1:14 ` Aaron Williams
2011-01-28 1:43 ` [U-Boot] [PATCH 1/1] NAND " Aaron Williams
2011-01-31 23:15 ` Aaron Williams
2011-01-31 23:28 ` Scott Wood
2011-02-01 2:56 ` [U-Boot] [PATCH 1/1] NAND Re: mtdparts fails with NAND >= 4GB - Second try Aaron Williams
2011-02-07 22:58 ` Scott Wood
2011-02-08 15:38 ` Andrew Dyer
2011-02-08 23:11 ` Aaron Williams
2011-02-09 1:56 ` Aaron Williams
[not found] ` <201102092228.40033.Aaron.Williams@caviumnetworks.com>
[not found] ` <AANLkTi=fsZXQjRFaZcB535n853WUxEicFqyzquWzMX41@mail.gmail.com>
2011-02-11 3:24 ` Aaron Williams
2011-02-11 3:27 ` Aaron Williams
2011-02-11 4:05 ` Aaron Williams
2011-02-12 0:15 ` Aaron Williams
2011-02-12 6:25 ` Albert ARIBAUD
2011-02-12 6:42 ` Aaron Williams
2011-02-12 7:01 ` Albert ARIBAUD
2011-02-12 7:06 ` Aaron Williams
2011-02-12 7:14 ` Aaron Williams
2011-02-12 7:51 ` Albert ARIBAUD
2011-02-12 7:57 ` Aaron Williams
2011-02-12 8:49 ` Albert ARIBAUD
2011-02-12 8:54 ` Aaron Williams
2011-02-12 10:08 ` Albert ARIBAUD
2011-02-12 12:06 ` Aaron Williams [this message]
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=201102120406.01194.Aaron.Williams@caviumnetworks.com \
--to=aaron.williams@caviumnetworks.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