From: Phil Blundell <pb@pbcl.net>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] "sub" machine types?
Date: Sun, 06 Sep 2015 21:45:34 +0100 [thread overview]
Message-ID: <1441572334.1680.77.camel@pbcl.net> (raw)
In-Reply-To: <55EA8F5B.408@dresearch-fe.de>
On Sat, 2015-09-05 at 08:44 +0200, Steffen Sledz wrote:
> What we wish is one image containing one kernel and device tree files for each product.
If these devices all use the same kernel and the same rootfs then it
sounds like, as far as OE is concerned, they are the same MACHINE. If
you need to build device trees and different bootloaders for particular
variants then you can do that easily enough with custom recipes.
p.
next prev parent reply other threads:[~2015-09-06 20:45 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 [this message]
2015-09-05 11:29 ` Mike Looijmans
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=1441572334.1680.77.camel@pbcl.net \
--to=pb@pbcl.net \
--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