From: "Jan Lübbe" <jlu@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Howto add platform specific image creation step
Date: Mon, 24 Sep 2012 14:58:21 +0200 [thread overview]
Message-ID: <1348491501.3491.18.camel@coredoba.hi.pengutronix.de> (raw)
In-Reply-To: <50605488.1060908@tqsc.de>
Hi,
On Mon, 2012-09-24 at 14:39 +0200, Markus Niebel wrote:
> is there a way to create 2 (or more) images for one platform but
> different media types (like SD-Card and eMMC)?
>
> Use cases:
>
> 1) Hardware platform is bootable from SD-card and eMMC etc. Kernel,
> Rootfs are the same. Only small differences in bootloader (Barebox)
> and bootloader environment.
>
> 2) Hardware platform has configuration options (RAM-size etc.)
>
> It is relative easy to build the bootloader twice ore more when simply
> copying and renaming / adapting the Kconfig and make rule in project
> local rules (as a hack for the first try). But in ptxd_make_bootable
> image names are hard coded.
This is possible with new new image generation support. Take a look at
"ptxdist newpackage barebox" and "ptxdist newpackage image-genimage".
Also, for examples you can look in:
http://git.pengutronix.de/?p=platform-pengutronix-beagleboneti.git
http://git.pengutronix.de/?p=platform-pengutronix-raspberrypi.git
config/images, platforms and rules are the relevant directories.
Regrads,
Jan
--
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 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-09-24 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 12:39 Markus Niebel
2012-09-24 12:58 ` Jan Lübbe [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=1348491501.3491.18.camel@coredoba.hi.pengutronix.de \
--to=jlu@pengutronix.de \
--cc=ptxdist@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