Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Lee Nipper <lee.nipper@linux.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: "sub" machine types?
Date: Wed, 9 Sep 2015 15:37:56 +0200	[thread overview]
Message-ID: <55F03634.1050609@dresearch-fe.de> (raw)
In-Reply-To: <CALg11mjA1HpV7eGBZ0c2bsATPmBb-oDpLBhF-ZWuUy8niY9TPQ@mail.gmail.com>

On 07.09.2015 16:24, Lee Nipper wrote:
> 
> On Mon, Sep 7, 2015 at 7:08 AM, Steffen Sledz <sledz@dresearch-fe.de <mailto:sledz@dresearch-fe.de>> wrote:
> 
>     On 07.09.2015 09:09, Steffen Sledz wrote:
>     > On 05.09.2015 13:29, Mike Looijmans wrote:
>     >> ... and I think the u-boot recipe recently learned to have multiple targets, so you can build multiple bootloaders for a single machine too.
>     >
>     > That sounds great. Can someone give a pointer to some documentation or examples for that?
> 
>     Is it correct to just replace the UBOOT_MACHINE item in the machine config with something like this?
> 
>     UBOOT_CONFIG ??= "sub1 sub2 sub3"
>     UBOOT_CONFIG[sub1] = "mymachine_sub1_config"
>     UBOOT_CONFIG[sub2] = "mymachine_sub2_config"
>     UBOOT_CONFIG[sub3] = "mymachine_sub3_config"
> 
> 
> Looks right.

What about the u-boot-fw-utils? Is the recipe ready for this too?

What about the artefacts? Is there one binary usable for all u-boot images?

-- 
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


      reply	other threads:[~2015-09-09 13:37 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
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 [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=55F03634.1050609@dresearch-fe.de \
    --to=sledz@dresearch-fe.de \
    --cc=lee.nipper@linux.com \
    --cc=mike.looijmans@topic.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox