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