From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] ARM: at91: change nand flash table
Date: Thu, 21 Feb 2013 14:58:45 +0800 [thread overview]
Message-ID: <5125C5A5.6000002@atmel.com> (raw)
In-Reply-To: <20130221020505.GP12654@bill-the-cat>
Hi Tom,
On 2/21/2013 10:05, Tom Rini wrote:
> On Wed, Feb 20, 2013 at 06:16:25PM +0800, Bo Shen wrote:
>
>> Change nand flash partition tablke according to www.at91.com/linux4sam
>>
>> more information: http://www.at91.com/linux4sam/bin/view/Linux4SAM/GettingStarted#Linux4SAM_NandFlash_demo_Memory
>>
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>
> Question. Is there a reason to not being doing the MTDIDS / MTDPARTS
> and adding CONFIG_CMD_MTDPARTS ?
Yes, MTDIDS/MTDPARTS is missing, however, we can set mtdids and mtdpart
environment to use mtdparts command. (Maybe this is not a good idea,
will consider to add MTDIDS / MTDPARTS later, not in this patch series.)
> Doing that should also "just" enable
> the nand info to be passed in the device tree.
I am not fully understand this. You means add MTDIDS / MTDPARTS, it can
automatically pass the nand info to device tree, not through the command
line, am I right?
Best Regards,
Bo Shen
next prev parent reply other threads:[~2013-02-21 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 10:16 [U-Boot] [PATCH 0/3] add libfdt bootz support and change nand partition table Bo Shen
2013-02-20 10:16 ` [U-Boot] [PATCH 1/3] arm: at91/configs: add libfdt to configuration Bo Shen
2013-03-12 11:59 ` [U-Boot] [U-Boot, " andreas.devel at googlemail.com
2013-02-20 10:16 ` [U-Boot] [PATCH 2/3] arm: at91/configs: add bootz " Bo Shen
2013-03-12 11:59 ` [U-Boot] [U-Boot, " andreas.devel at googlemail.com
2013-02-20 10:16 ` [U-Boot] [PATCH 3/3] ARM: at91: change nand flash table Bo Shen
2013-02-21 2:05 ` Tom Rini
2013-02-21 6:58 ` Bo Shen [this message]
2013-02-21 14:24 ` Tom Rini
2013-03-12 12:01 ` [U-Boot] [U-Boot,3/3] " andreas.devel at googlemail.com
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=5125C5A5.6000002@atmel.com \
--to=voice.shen@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.