From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 00/10] HiKey and DE0 Nano SoC boards, further improvements and cleanups
Date: Tue, 6 Nov 2018 11:51:39 +0100 [thread overview]
Message-ID: <65ee1954-cb39-f38c-65f9-9eb29519a50a@siemens.com> (raw)
In-Reply-To: <20181106104918.GB11201@yssyq.m.ilbers.de>
On 06.11.18 11:49, Baurzhan Ismagulov wrote:
> On Tue, Nov 06, 2018 at 12:59:33PM +0300, Maxim Yu. Osipov wrote:
>> We need to discuss which boards have to present in isar mainline.
>>
>> Should we include in isar (like in yocto) only several widespread reference
>> boards (like Raspberry Pis, BeagleBone Black etc) and support for other
>> boards should be shipped separately?
>>
>> Or these HiKey and DE0 Nano SoC are declared as reference boards?
>>
>> My concern is that growing number of supported boards in mainline will soon
>> litter the isar tree.
>
> I suggest to include this as is and look at the broader meta restructuring
> discussion of the last weeks after that.
Right, these boards should not be considered "core". They first of all help
testing more features of the core (meta). We may still decide to migrate
meta-isar into a separate repo or create some meta-isar-boards layer when things
start to grow.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-06 10:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 6:52 Jan Kiszka
2018-11-05 6:52 ` [PATCH 01/10] meta: builchroot: Preserve environment when calling dpkg-buildpackage Jan Kiszka
2018-11-05 9:41 ` Henning Schild
2018-11-05 9:46 ` Jan Kiszka
2018-11-05 10:05 ` Henning Schild
2018-11-05 10:16 ` [PATCH v2 " Jan Kiszka
2018-11-05 14:15 ` [PATCH " Baurzhan Ismagulov
2018-11-05 14:25 ` Jan Kiszka
2018-11-05 15:36 ` Henning Schild
2018-11-06 10:53 ` Baurzhan Ismagulov
2018-11-05 6:52 ` [PATCH 02/10] meta-isar: Remove remaining wheezy traces Jan Kiszka
2018-11-09 14:22 ` Baurzhan Ismagulov
2018-11-05 6:52 ` [PATCH 03/10] meta-isar: linux: Update mainline recipe to 4.19 Jan Kiszka
2018-11-05 6:52 ` [PATCH 04/10] meta-isar: example-module: Only disable cross-compilation for Debian kernels Jan Kiszka
2018-11-05 6:52 ` [PATCH 05/10] meta-isar: Add Terasic DE0-Nano-SoC as demonstration board Jan Kiszka
2018-11-05 6:52 ` [PATCH 06/10] meta-isar: Add LeMaker HiKey board Jan Kiszka
2018-11-05 6:52 ` [PATCH 07/10] meta: linux-module: Fix arm64 cross-build Jan Kiszka
2018-11-05 6:52 ` [PATCH 08/10] wic: bootimg-efi-isar: Avoid append "None" to kernel command line Jan Kiszka
2018-11-05 6:52 ` [PATCH 09/10] wic: bootimg-efi-isar: Make agnostic to partition order Jan Kiszka
2018-11-05 6:52 ` [PATCH 10/10] image: Add install_image_deps to cache_base_repo dependencies Jan Kiszka
2018-11-06 9:59 ` [PATCH 00/10] HiKey and DE0 Nano SoC boards, further improvements and cleanups Maxim Yu. Osipov
2018-11-06 10:49 ` Baurzhan Ismagulov
2018-11-06 10:51 ` Jan Kiszka [this message]
2018-11-07 13:11 ` Maxim Yu. Osipov
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=65ee1954-cb39-f38c-65f9-9eb29519a50a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
/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