From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [NEXT PATCH v1 2/7] NAND: added NAND type to nand_ids
Date: Mon, 10 Sep 2012 18:18:29 -0500 [thread overview]
Message-ID: <504E7545.10402@freescale.com> (raw)
In-Reply-To: <504DD871.7040301@denx.de>
On 09/10/2012 07:09 AM, Stefano Babic wrote:
> On 07/09/2012 20:56, Scott Wood wrote:
>> What kind of chip is this? Is the datasheet publicly available?
>>
>> These threads seem relevant:
>> http://patchwork.ozlabs.org/patch/60042/
>> http://old.nabble.com/-U-Boot--Add-new-NAND-flash-td29858370.html
>
> It is the same case, as I can see, with the same chip.
>
>>
>> Does the chip support ONFI?
>
> The chip supports ONFI, but it seems the i.MX driver does not. Quite as
> described in http://patchwork.ozlabs.org/patch/60042/. READ-ID is always
> sent with address 0, I do not know if we can convince the driver to send
> the address.
How did Linux end up resolving this? I think it'd be better to have the
Micron decoding logic from that patch, than to introduce a special
addition to the ID table for this one chip, which might not be correct
for all chips with that ID byte.
Or, we could treat it as information to be supplied by platform code (or
the device tree).
-Scott
next prev parent reply other threads:[~2012-09-10 23:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 8:04 [U-Boot] [NEXT PATCH v1 0/7] In this patchset, a new i.MX35 board is added implementing Stefano Babic
2012-09-06 8:04 ` [U-Boot] [NEXT PATCH v1 1/7] ARM: Fix start.S when used with SPL in arm1136 Stefano Babic
2012-09-06 8:04 ` [U-Boot] [NEXT PATCH v1 2/7] NAND: added NAND type to nand_ids Stefano Babic
2012-09-06 23:19 ` Scott Wood
2012-09-07 9:12 ` Stefano Babic
2012-09-07 15:23 ` Stefano Babic
2012-09-07 18:56 ` Scott Wood
2012-09-10 12:09 ` Stefano Babic
2012-09-10 23:18 ` Scott Wood [this message]
2012-10-01 7:02 ` Stefano Babic
2012-09-23 19:01 ` Eric Bénard
2012-09-24 8:29 ` Stefano Babic
2012-09-06 8:04 ` [U-Boot] [NEXT PATCH v1 3/7] MX35: add LOW_LEVEL_SRAM_STACK to use SPL_FRAMEWORK Stefano Babic
2012-09-06 8:04 ` [U-Boot] [NEXT PATCH v1 4/7] MX35: Add soc_boot_mode and soc_boot_device to MX35 Stefano Babic
2012-09-23 19:25 ` Eric Bénard
2012-09-24 8:35 ` Stefano Babic
2012-09-06 8:04 ` [U-Boot] [NEXT PATCH v1 5/7] SPL: Added MLO for mx35 SOC to SPL Makefile Stefano Babic
2012-09-06 17:49 ` Tom Rini
2012-09-06 19:59 ` Stefano Babic
2012-09-06 20:48 ` Tom Rini
2012-09-06 21:57 ` stefano babic
2012-09-10 12:27 ` Thomas Petazzoni
2012-09-10 12:44 ` Stefano Babic
2012-09-10 12:54 ` Tom Rini
2012-09-06 8:04 ` [U-Boot] [NEXT PATCH v1 6/7] ARM: Add MLO target to arm1136 Stefano Babic
2012-09-06 8:05 ` [U-Boot] [NEXT PATCH v1 7/7] MX35: add support for woodburn board Stefano Babic
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=504E7545.10402@freescale.com \
--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