Micron NAND support in linux MTD

[Ram]

Hi,
   The location of the "bad block indicator" within the spare area
depends on the
    manufacturer. It could vary from chip to chip.

   it could also depend on the page size as well.

   Usually, for a large page size nand, It could be located at the
first byte of the OOB.
   For a small it could be at 6th byte.

  The way you send some commands to the large page size nand device is
somewhat different
  from the small page size nand device. I think you may not be using
the driver for a large page  nand device.

  Most of the stuff (driver) for the large page nand devices is
generic. The way you wait for nand busy changes.

  Check the way your reading the flash information from the chip id
and additional infomation.
  The way youre mtd_info structure is getting initialised. You could
be missing something here.

Hope this helps.

Regards,
sriram




On Jan 18, 2008 3:48 PM, llandre <r&d2 at dave-tech.it> wrote:
> Hi,
>
> I found on MTD mailing list your patch that adds Micron manufacturer ID:
> http://article.gmane.org/gmane.linux.drivers.mtd/17694
>
> I'm going to use NAND Micron devices for a new project however I still
> have a doubt about how MTD/JFFS2 handle bad blocks. To detect blocks
> marked as bad it checks the 6th location of OOB area of first page, thus
> it seems it is not able to handle Micron devices properly. In fact these
> devices stores bad block marker in the first location of OOB of first or
> second page (for example see page 50 of MT29F1GxxABB data sheet). Am I
> misreading the datasheet? Could you help me to clear this point?
>
>
> Thanks in advance,
> llandre
>
> DAVE Electronics System House - R&D Department
> web:   http://www.dave-tech.it
> email: r&d2 at dave-tech.it
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>