From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Brian Lilly <brian@crystalfontz.com>
Subject: Re: [PATCH 1/2] Add support for kernel and device tree images stored in a partition
Date: Tue, 03 Jul 2012 13:18:49 +0200 [thread overview]
Message-ID: <4FF2D519.60305@free-electrons.com> (raw)
In-Reply-To: <20120703073926.GU2698@pengutronix.de>
Hi Sascha,
Le 03/07/2012 09:39, Sascha Hauer a écrit :
> On Mon, Jul 02, 2012 at 04:14:53PM +0200, Maxime Ripard wrote:
>> It is a quite common setup to have a partition with all you need to boot
>> from the bootloader, ie the kernel image, the device tree blob, etc.
>>
>> This patch introduces a new "file" location for these two images, which
>> uses in turn the *_part and the new *_part_type variable specifying the
>> fs type used by mount.
>
> That was one of the major shortcomings of the default environment and
> one of the main reasons I created a new environment template. Have you
> considered using it?
Ha, I think I missed it :)
It looks quite useful indeed.
I will drop this patch then and send an updated version once I'll be
able to use it properly.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-07-03 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 14:14 Maxime Ripard
2012-07-02 14:14 ` [PATCH 2/2] Add support for the Crystalfontz CFA-10036 board Maxime Ripard
2012-07-03 18:12 ` Sascha Hauer
2012-07-04 12:28 ` Maxime Ripard
2012-07-02 17:30 ` [PATCH 1/2] Add support for kernel and device tree images stored in a partition Belisko Marek
2012-07-03 7:39 ` Sascha Hauer
2012-07-03 11:18 ` Maxime Ripard [this message]
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=4FF2D519.60305@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=barebox@lists.infradead.org \
--cc=brian@crystalfontz.com \
--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