From: Steffen Sledz <sledz@dresearch-fe.de>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-core <openembedded-core@lists.openembedded.org>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] "sub" machine types?
Date: Mon, 7 Sep 2015 09:09:50 +0200 [thread overview]
Message-ID: <55ED383E.6070005@dresearch-fe.de> (raw)
In-Reply-To: <55EAD217.3010806@topic.nl>
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?
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Steffen Sledz <sledz@dresearch-fe.de>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-core <openembedded-core@lists.openembedded.org>,
openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: "sub" machine types?
Date: Mon, 7 Sep 2015 09:09:50 +0200 [thread overview]
Message-ID: <55ED383E.6070005@dresearch-fe.de> (raw)
In-Reply-To: <55EAD217.3010806@topic.nl>
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?
--
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
next prev parent reply other threads:[~2015-09-07 7:09 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 ` [OE-core] " Steffen Sledz
2015-09-05 6:44 ` [oe] " 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 ` Steffen Sledz [this message]
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=55ED383E.6070005@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--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 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.