From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 31 Mar 2009 12:20:06 -0500 Subject: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM) In-Reply-To: <528f13590903311004n6b93563an85d8e273a828393e@mail.gmail.com> References: <528f13590903270907xde6a90fn5e3614578ae2fe75@mail.gmail.com> <59b21cf20903271152q4efb7527g32e80f3749bca450@mail.gmail.com> <528f13590903271211j7677539cq975c51618a76e810@mail.gmail.com> <59b21cf20903271301m54ea84cfycde5976ba504b687@mail.gmail.com> <528f13590903300948k62a69c3fge00afc09bb93a5af@mail.gmail.com> <20090330173529.GA28844@ld0162-tx32.am.freescale.net> <528f13590903301821h2f749a9eoef821abfd0dc3c2b@mail.gmail.com> <528f13590903311004n6b93563an85d8e273a828393e@mail.gmail.com> Message-ID: <49D250C6.5000603@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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