New NAND Help

[Eric Millbrandt]

> -----Original Message-----
> From: linux-mtd-bounces at lists.infradead.org [mailto:linux-mtd-
> bounces at lists.infradead.org] On Behalf Of Sean Preston
> Sent: Thursday, July 08, 2010 08:47
> To: Linux-MTD List
> Subject: New NAND Help
>
<snip>
>
> Looking at the drivers/mtd/nand section of the tree I have added the new
> chip ID to nand_ids.c  There already appears to be support for 4096 page
> sizes and 512K block sizes.  What else would I need to check to ensure
> that
> the kernel is able to probe this chip and load the driver needed for it.
> The driver currently being loaded is the davinci_nand driver.  I have
> managed to get this chip working with uBoot which uses a modified version
> of
> the MTD driver.
>
I found that some of the newer Micron nand chips don't store information about the chip layout in the id block anymore.  It's all been moved to the parameter page.  nand_get_flash_type(), in nand_base.c, relies on that data to correctly describe the chip layout, so you may need to hardcode the pagesize and eraseblock size in the nand_flash_ids table.

Take a look at the READ ID operation section in the micron datasheet to see if the relevant data is still exists, otherwise you need to hardcode those values.

Eric

-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

> Regards
> Sean
>
> --
> Sean Preston
> Email: seanp at pfk.co.za
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.