All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] "sub" machine types?
Date: Sat, 5 Sep 2015 08:44:43 +0200	[thread overview]
Message-ID: <55EA8F5B.408@dresearch-fe.de> (raw)
In-Reply-To: <CAP71Wjzcr_ByLfCnAgQ3t2MYv+D88iTL5_VJ4Cdn23iAnyHfhg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 04.09.2015 um 09:45 schrieb Nicolas Dechesne:
> On Fri, Sep 4, 2015 at 9:35 AM, Steffen Sledz <sledz@dresearch-fe.de> 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?
> 
> most BSP layers use SOC_FAMILY, see [1] for this type of things, such that you can create 'SOC' specific packages that are reused across multiple (OE) machines. That sounds like that would help in your situation.
> 
> [1] http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-SOC_FAMILY

I'm not really sure if this is what we need. You suggest to use different MACHINEs of one SOC_FAMILY, Right?

But if I bitbake the root filesystem for each MACHINE an *own* image is created. And not *one* usable for all of them.

What we wish is one image containing one kernel and device tree files for each product.

In addition a u-boot image for each product so that we can use a boot setup running different u-boot images starting the same kernel and root filesystem with different parameters (e.g. for the device trees).

- -- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJV6o9aAAoJEIz5slJ1krPhF9UP/0cp0JrohbZOeRen1ksJfGIr
J3kGKKEqBlw4s+0ugsPIMSp3pR2La/7/IgGV938H5mc6+88CobTpQU25TaE31ukq
hgfoG/SHuZCucp1TpTahANkt+d8OmrDOTDLYTzEmWD47VGRp64PiMzlQBKIg27Bo
NUdG3cFoUzPrS6tu24LR/EiM+ve2+ItZ8/pEXY0RiCYD/vhehP8qq2Yunow5cvyj
xvy1kxbJYCYvjXQF52z9L+R68vvZVzXFF7VrTeT00DJlj99KP5R97vvbIyHzFsHK
1YJfmRkkSx5d41QGegM9GHJGaGOKxHQekh/V5PgwfgQKBxgXq/5slWAvIzH7l6Fq
udkqX9goeeEmkztiUhK1VbEQr8wd5SyRI/9wfEJD8AuJPiV460JZrC2lhh/dOxnf
sEOGzgNMe/lddcGty6ns5Jn9ztJhnaYNtYK1NFdY/aGUPASgcXCCcPxUNW00KEsp
yCwmVEUE37vIGJltqJ2XfUCPhIZ4eiuPZOkzYHo4s+CtArKHiWlzWWREXSrNREql
92FDTuOCkBuYDrmiRMbIuHRxO7gguE2ZS8YPCSRbGsE/VwwUhlMAtRddnGr5QA1G
FL1qnW+28wrqwHZlVfzFzO+qUnAo7/LqfnF525ABObdlF6sk4/b9r2MeTEoPwLkx
qd2HFZDh4HBu2h4t6E1s
=m/r6
-----END PGP SIGNATURE-----


WARNING: multiple messages have this Message-ID (diff)
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] "sub" machine types?
Date: Sat, 5 Sep 2015 08:44:43 +0200	[thread overview]
Message-ID: <55EA8F5B.408@dresearch-fe.de> (raw)
In-Reply-To: <CAP71Wjzcr_ByLfCnAgQ3t2MYv+D88iTL5_VJ4Cdn23iAnyHfhg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 04.09.2015 um 09:45 schrieb Nicolas Dechesne:
> On Fri, Sep 4, 2015 at 9:35 AM, Steffen Sledz <sledz@dresearch-fe.de> 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?
> 
> most BSP layers use SOC_FAMILY, see [1] for this type of things, such that you can create 'SOC' specific packages that are reused across multiple (OE) machines. That sounds like that would help in your situation.
> 
> [1] http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-SOC_FAMILY

I'm not really sure if this is what we need. You suggest to use different MACHINEs of one SOC_FAMILY, Right?

But if I bitbake the root filesystem for each MACHINE an *own* image is created. And not *one* usable for all of them.

What we wish is one image containing one kernel and device tree files for each product.

In addition a u-boot image for each product so that we can use a boot setup running different u-boot images starting the same kernel and root filesystem with different parameters (e.g. for the device trees).

- -- 
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJV6o9aAAoJEIz5slJ1krPhF9UP/0cp0JrohbZOeRen1ksJfGIr
J3kGKKEqBlw4s+0ugsPIMSp3pR2La/7/IgGV938H5mc6+88CobTpQU25TaE31ukq
hgfoG/SHuZCucp1TpTahANkt+d8OmrDOTDLYTzEmWD47VGRp64PiMzlQBKIg27Bo
NUdG3cFoUzPrS6tu24LR/EiM+ve2+ItZ8/pEXY0RiCYD/vhehP8qq2Yunow5cvyj
xvy1kxbJYCYvjXQF52z9L+R68vvZVzXFF7VrTeT00DJlj99KP5R97vvbIyHzFsHK
1YJfmRkkSx5d41QGegM9GHJGaGOKxHQekh/V5PgwfgQKBxgXq/5slWAvIzH7l6Fq
udkqX9goeeEmkztiUhK1VbEQr8wd5SyRI/9wfEJD8AuJPiV460JZrC2lhh/dOxnf
sEOGzgNMe/lddcGty6ns5Jn9ztJhnaYNtYK1NFdY/aGUPASgcXCCcPxUNW00KEsp
yCwmVEUE37vIGJltqJ2XfUCPhIZ4eiuPZOkzYHo4s+CtArKHiWlzWWREXSrNREql
92FDTuOCkBuYDrmiRMbIuHRxO7gguE2ZS8YPCSRbGsE/VwwUhlMAtRddnGr5QA1G
FL1qnW+28wrqwHZlVfzFzO+qUnAo7/LqfnF525ABObdlF6sk4/b9r2MeTEoPwLkx
qd2HFZDh4HBu2h4t6E1s
=m/r6
-----END PGP SIGNATURE-----


  reply	other threads:[~2015-09-05  6:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  7:35 "sub" machine types? Steffen Sledz
2015-09-04  7:45 ` Nicolas Dechesne
2015-09-04  7:45   ` [oe] " Nicolas Dechesne
2015-09-05  6:44   ` Steffen Sledz [this message]
2015-09-05  6:44     ` Steffen Sledz
2015-09-06 20:45     ` Phil Blundell
2015-09-05 11:29 ` [OE-core] " Mike Looijmans
2015-09-05 11:29   ` Mike Looijmans
2015-09-07  7:09   ` [OE-core] " Steffen Sledz
2015-09-07  7:09     ` Steffen Sledz
2015-09-07 12:08     ` [OE-core] " Steffen Sledz
2015-09-07 12:08       ` Steffen Sledz
2015-09-07 14:24       ` Lee Nipper
2015-09-09 13:37         ` [OE-core] " Steffen Sledz
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=55EA8F5B.408@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.