From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm : Atmel : add at91sam9x5ek board support
Date: Mon, 02 Jul 2012 12:02:56 +0200 [thread overview]
Message-ID: <4FF171D0.2000309@gmail.com> (raw)
In-Reply-To: <4FF16F9C.3050101@atmel.com>
Dear all,
On 02.07.2012 11:53, Nicolas Ferre wrote:
> On 07/02/2012 11:47 AM, Andreas Bie?mann :
>> On 02.07.2012 10:36, Bo Shen wrote:
>
> [..]
>
>>>>> +/* bootstrap + u-boot + env + linux in nandflash */
>>>>> +#define CONFIG_ENV_IS_IN_NAND
>>>>> +#define CONFIG_ENV_OFFSET 0xc0000
>>>>> +#define CONFIG_ENV_OFFSET_REDUND 0x100000
>>>>> +#define CONFIG_ENV_SIZE 0x20000 /* 1 sector = 128 kB */
>>>>> +#define CONFIG_BOOTCOMMAND "nand read.jffs2 " \
>>>>> + "0x22000000 0x200000 0x300000; " \
>>>>> + "bootm 0x22000000"
>>>>
>>>> Well, you read from jffs but work with ubifs later on? Is that ok?
>>>> BTW: I do not know 'nand read.jffs2', does this subcommand exist really?
>>>
>>> Using the read with subfix .jffs2 it to skip the bad block. This
>>> partition is for Linux kernel.
>>> I will remove the .jffs2 to avoid confusing.
>>
>> Well, it is ok with me to use read.jffs2 (if it works). I just do not
>> know about that subcommand and I can only find some references about
>> that in two other boards. I guess these boards are just forgotten while
>> removing the 'nand read.jffs2' command. Please check, if that command
>> works, if yes let it as is, if not rewrite.
>
> I am in favor of using read.jffs2 because it is able to skip bad blocks.
> As the programming tool is also skipping bad blocks the same way, we
> have a configuration that is perfectly working even in case of bad block
> in the middle of the kernel image.
>
> So please, keep using read.jffs2 (or equivalent)!
I have the same opinion here, we should skip bad blocks. But I think
'nand read.jffs2' is not available any longer.
from current common/cmd_nand.c:
---8<---
"nand read - addr off|partition size\n"
"nand write - addr off|partition size\n"
" read/write 'size' bytes starting@offset 'off'\n"
" to/from memory address 'addr', skipping bad blocks.\n"
"nand read.raw - addr off|partition [count]\n"
"nand write.raw - addr off|partition [count]\n"
" Use read.raw/write.raw to avoid ECC and access the flash as-is.\n"
--->8---
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2012-07-02 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 3:35 [U-Boot] [PATCH v2] arm : Atmel : add at91sam9x5ek board support Bo Shen
2012-07-02 7:01 ` Andreas Bießmann
2012-07-02 8:36 ` Bo Shen
2012-07-02 9:47 ` Andreas Bießmann
2012-07-02 9:53 ` Nicolas Ferre
2012-07-02 10:02 ` Andreas Bießmann [this message]
2012-07-02 10:08 ` Nicolas Ferre
2012-07-02 10:23 ` Andreas Bießmann
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=4FF171D0.2000309@gmail.com \
--to=andreas.devel@googlemail.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