From: RONETIX - Asen Dimov <dimov@ronetix.at>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/4] pm9g45: boot from NAND
Date: Wed, 21 Mar 2012 18:43:32 +0200 [thread overview]
Message-ID: <4F6A0534.3060808@ronetix.at> (raw)
In-Reply-To: <20120308130529.GN12248@game.jcrosoft.org>
Hi Jean-Christophe,
I am back on the pm9g45 patches again.
On 03/08/2012 03:05 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:37 Thu 08 Mar , RONETIX - Asen Dimov wrote:
>> Hi Jean-Christophe,
>>
>> On 03/02/2012 07:18 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>
>> In the "defaultenv/bin/boot" it is mentioned "/dev/nand0.kernel.bb"
>> and many boards are using
>> ".bb" suffix.
> no the name need to be kernel
>
> the .dd will be add automatically for the bad bloack aware device
> so you loose space
In the pm9g45 v3 patch series the MTD partition for Linux is named
"kernel", and "defaultenv/bin/boot"
script looks for "/dev/nand0.kernel.bb". In the same time all boards
name Linux MTD partition
"kernel.bb". Is this "bad block aware device" driver scheduled to be
implemented in barebox or
is it allowable to rename that partition to "kernel.bb" to un-broke the
boot process?
> Best Regards,
> J.
Regards,
Asen
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-03-21 16:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 16:21 [PATCH 1/3] pm9g45: fix Ethernet Asen Chavdarov Dimov
2012-03-01 16:21 ` [PATCH 2/3] pm9g45: enable MCI0 Asen Chavdarov Dimov
2012-03-01 17:10 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-01 16:21 ` [PATCH 3/3] pm9g45: enable USB OHCI host and USB mass storage Asen Chavdarov Dimov
2012-03-01 17:12 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-02 15:20 ` RONETIX - Asen Dimov
2012-03-02 17:13 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-01 17:08 ` [PATCH 1/3] pm9g45: fix Ethernet Jean-Christophe PLAGNIOL-VILLARD
2012-03-02 16:55 ` [PATCH v2 1/4] pm9g45: boot from NAND Asen Chavdarov Dimov
2012-03-02 16:55 ` [PATCH v2 2/4] pm9g45: fix Ethernet Asen Chavdarov Dimov
2012-03-02 17:19 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-02 16:55 ` [PATCH v2 3/4] pm9g45: enable MCI0 Asen Chavdarov Dimov
2012-03-02 17:21 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-02 16:55 ` [PATCH v2 4/4] pm9g45: enable USB OHCI host and USB mass storage Asen Chavdarov Dimov
2012-03-02 17:22 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-02 17:18 ` [PATCH v2 1/4] pm9g45: boot from NAND Jean-Christophe PLAGNIOL-VILLARD
2012-03-08 11:37 ` RONETIX - Asen Dimov
2012-03-08 13:05 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-21 16:43 ` RONETIX - Asen Dimov [this message]
2012-03-21 16:27 ` [PATCH v3 " Asen Chavdarov Dimov
2012-03-21 16:27 ` [PATCH v3 2/4] pm9g45: fix Ethernet Asen Chavdarov Dimov
2012-03-21 16:27 ` [PATCH v3 3/4] pm9g45: enable MCI0 Asen Chavdarov Dimov
2012-03-22 20:17 ` Sascha Hauer
2012-03-23 12:55 ` RONETIX - Asen Dimov
2012-03-23 15:18 ` Sascha Hauer
2012-03-21 16:27 ` [PATCH v3 4/4] pm9g45: enable USB OHCI host and USB mass storage Asen Chavdarov Dimov
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=4F6A0534.3060808@ronetix.at \
--to=dimov@ronetix.at \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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