Thanks Again, I am actually confused with the values for chip size which should be the total chip size in MB w.r.t nand_flash_dev structure and "pagesize" as pagesize seems to be extended bytes alone in the datasheet which i am unable to figure of as of now. The pagesize seems to be different from the exact "pagesize" as in the data sheet for the other parts in include/linux/mtd/nand_ids.h. Do you know what to look for in the data sheet .
On Tue, Mar 31, 2009 at 2:10 PM, alfred steele <alfred.jaq...@gmail.com> wrote: > Hi Scott, > > Thanks! > The only requirement i have currently is to be able to populate the > device table with the "Samsung K9F1G08R0A" because it does not > appear in the existing list. This would help the NFC read the part id > and the other NAND attributes correctly on the target. > > Thanks & Regards. > > > On Tue, Mar 31, 2009 at 12:20 PM, Scott Wood <scottw...@freescale.com> wrote: >> alfred steele wrote: >>> >>> Hi Scott: >>> Thanks! >>> >>> >>>>> I am also wondering if there is a include file which builds up a table >>>>> of working NAND devices and thier attributes which tells the U-boot on >>>>> the parameters about a particular NAND device on the board like >>>>> Block_size , page_size, device size, pages per block, device id etc. >>>>> Or This information needs to be kind of hardcoded every time. >>>> >>>> drivers/mtd/nand/nand_ids.c >>> >>> I have three files which probably make sense to include the new flash >>> part. >>> drivers/mtd/nand/nand_ids.c >> >> This is the one. However, an individual NAND driver shouldn't have to care; >> it will be taken care of by the NAND subsystem. >> >>> ./common/cmd_doc.c >>> ./include/linux/mtd/nand_ids.h: >> >> Ignore these. They are legacy code that will soon be removed. >> >>> At this point, i do not understand the purpose of each and especially >>> how would the structure flash_id be populated from our data sheet for >>> the flash part we use >>> "Samsung K9F1G08R0A". >> >> Most likely it is already in the table. >> >>> I basically do not understand all the elements of the array >>> nand_flash_dev nand_flash_ids[] to be able to populate it correctly. >> >> Which field in particular are you unsure of? They are described in the >> definition of nand_flash_dev in include/linux/mtd/nand.h. >> >> Is there any reason why your NAND controller driver needs to care about any >> of this, as opposed to just hooking up to the NAND subsystem? >> >> -Scott >> > _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
