From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH 7/7] meta: Add barebox bootloader support
Date: Thu, 10 Feb 2022 09:05:04 +0100 [thread overview]
Message-ID: <f7c50399-588e-fc61-343e-df006a38d116@siemens.com> (raw)
In-Reply-To: <93d39911-dc1e-13ea-62fc-4af56dcef076@ilbers.de>
On 10.02.22 08:58, Anton Mikanovich wrote:
>>> diff --git a/meta/recipes-bsp/barebox/barebox_2021.04.0-phy5.bb
>>> b/meta/recipes-bsp/barebox/barebox_2021.04.0-phy5.bb
>>> new file mode 100644
>>> index 0000000..ed8842c
>>> --- /dev/null
>>> +++ b/meta/recipes-bsp/barebox/barebox_2021.04.0-phy5.bb
>>> @@ -0,0 +1,13 @@
>>> +# This software is a part of ISAR.
>>> +# Copyright (C) 2022 ilbers GmbH
>>> +
>>> +inherit dpkg
>>> +
>>> +require barebox.inc
>>> +
>>> +SRC_URI +=
>>> "https://git.phytec.de/barebox/snapshot/barebox-2021.04.0-phy5.tar.bz2 \
>> Do we really want to or have to promote downstream BSP anti-patterns
>> here? Upstream barebox does not work?
>>
>> I'm mentioning this as I worked hard to avoid that bad practice for the
>> TF-A, OP-TEE, and U-Boot examples we provide.
> Upstream barebox will probably need some patching.
> But it should be not so hard to adapt, so I can try.
If upstream barebox is incomplete then why use it? Upstream U-Boot works
on that board (that's why we used it so far).
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-02-10 8:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:54 [PATCH 0/7] Rebuild phyBOARD-Mira UBI image generation Anton Mikanovich
2022-02-09 13:54 ` [PATCH 1/7] ubi: Move default output paths to image class Anton Mikanovich
2022-02-09 13:54 ` [PATCH 2/7] ubi: Remove isar-image-ubi Anton Mikanovich
2022-02-09 13:54 ` [PATCH 3/7] ubi: Move tasks reorder into parent task Anton Mikanovich
2022-02-09 13:54 ` [PATCH 4/7] ubi: Split UBI configs for phyboard-mira and imx6-sabrelite Anton Mikanovich
2022-02-09 13:54 ` [PATCH 5/7] conf: Remove machine-specific defines from multiconfig Anton Mikanovich
2022-02-09 13:54 ` [PATCH 6/7] meta-isar: Add linux-phy kernel Anton Mikanovich
2022-02-09 13:54 ` [PATCH 7/7] meta: Add barebox bootloader support Anton Mikanovich
2022-02-09 18:08 ` Jan Kiszka
2022-02-10 7:58 ` Anton Mikanovich
2022-02-10 8:05 ` Jan Kiszka [this message]
2022-02-10 8:45 ` Anton Mikanovich
2022-02-10 11:24 ` Jan Kiszka
2022-02-10 14:03 ` Anton Mikanovich
2022-02-10 6:52 ` [PATCH 0/7] Rebuild phyBOARD-Mira UBI image generation Schmidt, Adriaan
2022-02-10 8:12 ` Anton Mikanovich
2022-02-18 16:38 ` Anton Mikanovich
2022-03-31 6:10 ` Schmidt, Adriaan
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=f7c50399-588e-fc61-343e-df006a38d116@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--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