public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot NAND boot on IMX31 3stack(ARM)
Date: Tue, 31 Mar 2009 12:20:06 -0500	[thread overview]
Message-ID: <49D250C6.5000603@freescale.com> (raw)
In-Reply-To: <528f13590903311004n6b93563an85d8e273a828393e@mail.gmail.com>

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

  reply	other threads:[~2009-03-31 17:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 16:07 [U-Boot] U-boot NAND boot on IMX31 3stack(ARM) alfred steele
2009-03-27 18:52 ` Magnus Lilja
2009-03-27 19:11   ` alfred steele
2009-03-27 20:01     ` Magnus Lilja
2009-03-30 16:48       ` alfred steele
2009-03-30 17:35         ` Scott Wood
2009-03-31  1:21           ` alfred steele
2009-03-31 17:04             ` alfred steele
2009-03-31 17:20               ` Scott Wood [this message]
2009-03-31 19:09                 ` alfred steele
2009-03-31 19:10                 ` alfred steele
2009-03-31 19:28                   ` Scott Wood
2009-03-31 19:32                   ` alfred steele
2009-03-31 19:56                     ` Magnus Lilja
2009-03-31 20:45                     ` Scott Wood
2009-03-30 18:18         ` Magnus Lilja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D250C6.5000603@freescale.com \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox