On 03/08/2015 07:19 PM, Robert Jarzmik wrote:
> Ezequiel Garcia <[email protected]> writes:
>
>>> I think you'll kill the zylonite board, and I'll nack it if that's the
>>> case. At
>>> least that's what happened when I tried to use onfi default values last
>>> time in
>>> barebox development.
>>>
>>> I can test your changes, but if the specific zylonite nand (ie. nand id
>>> 0xba20,
>>> ie. pxa310 embedded flash) gets broken, I'm against the removal of the
>>> legacy
>>> timings removal.
>>>
>>
>> I'm not speaking of any timing params here, but about the flash
>> identification.
>>
>> Which flash do you have there?
> The one with 0xba20 id as I said, which is AFAIK a Numonyx NAND02GR4B2C.
>
$ grep "0xBA" drivers/mtd/nand/nand_ids.c
EXTENDED_ID_NAND("NAND 256MiB 1,8V 16-bit", 0xBA, 256, LP_OPTIONS16),
Seems already supported by the NAND core. The MTD way of probing
a non-ONFI device is by using the IDs in nand_ids.c. Additional
configuration (timings in this case) is applied between the nand_scan_ident()
and nand_scan_tail() calls.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
