From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
"Moessbauer, Felix (T CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Schmidt, Adriaan (T CED EDC-DE)" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH v3 2/3] deploy boot files via sstate-cache
Date: Wed, 10 Jan 2024 05:27:17 +0100 [thread overview]
Message-ID: <ae5a1f66-a37e-4f5c-9291-d8bb0a3fe427@siemens.com> (raw)
In-Reply-To: <84afbe6c-e561-4c57-9145-270ffa289686@ilbers.de>
On 09.01.24 15:04, Anton Mikanovich wrote:
> 09/01/2024 15:46, Jan Kiszka wrote:
>> Careful with renaming, I'm not sure of we aren't picking up the DTBs
>> from there and also relying on the names as the firmware will need
>> specific naming as well. This needs at least double-checking.
>>
>> Jan
>>
> It looks like there is no other solution, because different distros may
> have
> differencies in their dtb files.
> Downstreams are rely on Isar output paths, so we should at least create
> a item
> in RECIPE-API-CHANGELOG.md.
>
This is about naming for the kernel or the firmware, not for the layer.
Again: Careful! Also, it would likely be better to enhance
DEPLOY_DIR_IMAGE with the distro, rather than messing with the file names.
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-01-10 4:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 6:43 [PATCH v3 0/3] Fix data-race in deployment of initrd Felix Moessbauer
2023-02-23 6:43 ` [PATCH v3 1/3] add initramfs to sstate-cache Felix Moessbauer
2023-02-23 6:43 ` [PATCH v3 2/3] deploy boot files via sstate-cache Felix Moessbauer
2023-12-29 7:29 ` Anton Mikanovich
2024-01-09 12:46 ` MOESSBAUER, Felix
2024-01-09 13:46 ` Jan Kiszka
2024-01-09 14:04 ` Anton Mikanovich
2024-01-10 4:27 ` Jan Kiszka [this message]
2024-02-26 13:32 ` Uladzimir Bely
2024-02-26 18:17 ` MOESSBAUER, Felix
2023-02-23 6:43 ` [PATCH v3 3/3] fix race-cond between default and custom initrd Felix Moessbauer
2023-03-06 6:05 ` [PATCH v3 0/3] Fix data-race in deployment of initrd Uladzimir Bely
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=ae5a1f66-a37e-4f5c-9291-d8bb0a3fe427@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@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