From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Mon, 01 Oct 2012 09:02:30 +0200 Subject: [U-Boot] [NEXT PATCH v1 2/7] NAND: added NAND type to nand_ids In-Reply-To: <504E7545.10402@freescale.com> References: <1346918700-32429-1-git-send-email-sbabic@denx.de> <1346918700-32429-3-git-send-email-sbabic@denx.de> <50492F9B.2040205@freescale.com> <5049BA96.7000501@denx.de> <504A118D.8090808@denx.de> <504A434E.9020001@freescale.com> <504DD871.7040301@denx.de> <504E7545.10402@freescale.com> Message-ID: <50694006.1070009@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/09/2012 01:18, Scott Wood wrote: > 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. >> >>> Hi Scott, >>> 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 could take a closer look. The issue is not solved on linux, too. In fact, the MXC driver in current kernel supports ONFI, but it should work for newer version of the controller - I think with MX5. On MX35, the NFC controller is V1.1, exactly as on MX25, and I have the same issue reported by Matthias that you pointed out in the past threads: ONFI command does not work. > 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. Agree. I am trying to contact Micron to get some information about it. I have tried to decode the bytes on basis of other Micron's NAND, but then bit 6 in byte 4 says that the NAND is a 16 bit device, and that is wrong. Exactly the same wrong value that Matthias found some times ago. Stefano -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================