From: Mike Looijmans <mike.looijmans@topic.nl>
To: Steffen Sledz <sledz@dresearch-fe.de>,
openembedded-core <openembedded-core@lists.openembedded.org>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: "sub" machine types?
Date: Sat, 05 Sep 2015 13:29:27 +0200 [thread overview]
Message-ID: <55EAD217.3010806@topic.nl> (raw)
In-Reply-To: <55E949A4.9050805@dresearch-fe.de>
On 04-09-15 09:35, Steffen Sledz wrote:
> We have some products which differ in bootloaders (u-boot) and kernel device trees only. They use the same kernel and root filesystem.
>
> Does OE have concepts for this? Or any suggestions to realize this without building for many machines?
The way I handled this was to make it so that all machines have the same
MACHINE_ARCH, but MACHINE has some suffixes. This combines the kernels
and such. Only problem with that approach is that OE will erase the
kernel for a previous machine if you build for the next one, so you have
to copy the resulting images to another location at the end of the build.
For your case, I think you can just use a single MACHINE. You can just
supply multiple devicetrees, and I think the u-boot recipe recently
learned to have multiple targets, so you can build multiple bootloaders
for a single machine too.
--
Mike Looijmans
next prev parent reply other threads:[~2015-09-05 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 7:35 "sub" machine types? Steffen Sledz
2015-09-04 7:45 ` [oe] " Nicolas Dechesne
2015-09-05 6:44 ` Steffen Sledz
2015-09-06 20:45 ` Phil Blundell
2015-09-05 11:29 ` Mike Looijmans [this message]
2015-09-07 7:09 ` Steffen Sledz
2015-09-07 12:08 ` Steffen Sledz
2015-09-07 14:24 ` Lee Nipper
2015-09-09 13:37 ` Steffen Sledz
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=55EAD217.3010806@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=sledz@dresearch-fe.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