From: Doug Brainard <dbrainard@brainardinsight.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method.
Date: Thu, 12 Feb 2015 22:32:52 -0700 [thread overview]
Message-ID: <CA+nEJim28ognHA_ntd_pgr6UTuQAXdpMMiB4bwjuoK=EykyyuQ@mail.gmail.com> (raw)
In-Reply-To: <20150212091353.GQ12209@pengutronix.de>
Sascha,
I got the patching thing figured out and they seem to be working well
for me. I sent out a patch for the SAMA5D4EK new environment
requiring the patches you sent (fixing the naming issue).
Thanks,
Doug
On Thu, Feb 12, 2015 at 2:13 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Wed, Feb 11, 2015 at 10:39:52AM -0700, Doug Brainard wrote:
>> So it looks like the following line in mtdparts-add is causing the
>> "nand0." issue:
>>
>> addpart -n /dev/${device} "$parts" || exit
>>
>> The old environment didn't use the "-n". Removing the "-n" fixes the
>> issue and gives it the same functionality as the old environment did.
>>
>> So the question is how should I fix this? I could remove it in the
>> default environment, but that would require all other boards using the
>> new environment to update.
>>
>> Or, I can add my own env/bin/mtdparts-add script for the board and
>> remove the "-n" from there instead which would leave the other
>> projects alone. I'm assuming I should use this option as the fix, but
>> I wanted to confirm that with you.
>
> I would rather add a '-n' option to the mtdparts-add script. Anyway, I
> just sent a series updating the partition handling. Among other things
> I hope that this fixes the naming issue.
>
> Sascha
>
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-02-13 5:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 14:28 [PATCH 1/2] SAMA5D4EK - Now mostly supports booting Android from NAND Doug Brainard
2015-02-10 14:28 ` [PATCH 2/2] Switched SAMA5D4EK development board to the newer environment method Doug Brainard
2015-02-11 2:34 ` Bo Shen
2015-02-11 4:00 ` Doug Brainard
2015-02-11 5:06 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11 7:26 ` Bo Shen
2015-02-11 8:35 ` Sascha Hauer
2015-02-11 8:54 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11 9:12 ` Eric Bénard
2015-02-11 9:19 ` Sascha Hauer
2015-02-11 12:03 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11 14:33 ` Sascha Hauer
2015-02-11 8:43 ` Sascha Hauer
2015-02-11 16:53 ` Doug Brainard
2015-02-11 16:38 ` Doug Brainard
2015-02-11 17:39 ` Doug Brainard
2015-02-12 9:13 ` Sascha Hauer
2015-02-13 2:57 ` Doug Brainard
2015-02-13 5:32 ` Doug Brainard [this message]
2015-02-11 1:30 ` [PATCH 1/2] SAMA5D4EK - Now mostly supports booting Android from NAND Bo Shen
2015-02-11 4:02 ` Doug Brainard
2015-02-11 7:23 ` Bo Shen
2015-02-11 5:04 ` Jean-Christophe PLAGNIOL-VILLARD
2015-02-11 7:42 ` Sascha Hauer
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='CA+nEJim28ognHA_ntd_pgr6UTuQAXdpMMiB4bwjuoK=EykyyuQ@mail.gmail.com' \
--to=dbrainard@brainardinsight.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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