From: Paul Eggleton <bluelightning@bluelightning.org>
To: Martin Jansa <Martin.Jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Ming Liu <liu.ming50@gmail.com>, Marek Vasut <marex@denx.de>,
Andrej Valek <andrej.valek@siemens.com>,
Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>,
Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>,
Sean Anderson <sean.anderson@seco.com>,
George McCollister <george.mccollister@gmail.com>
Subject: Re: [OE-core] [RFC] [PATCH] Allow fitimage + initramfs rebuild to be accelerated
Date: Fri, 11 Nov 2022 09:21:24 +1300 [thread overview]
Message-ID: <3463540.iIbC2pHGDl@linc> (raw)
In-Reply-To: <CA+chaQdrSSoXccVRyWHNm=pX9jFV_SN-ucmBovu-=g_Y0FMNbw@mail.gmail.com>
On Thursday, 10 November 2022 08:53:02 NZDT Martin Jansa wrote:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=12937 might be
> alternative solution which we at LGE were using for different usecase than
> fit image, but in theory should work as well.
>
> Basically the initramfs do_deploy could be without version and then the
> hardlink with datetime (or any other version) is created in fast
> do_deploy_links task.
Unless I've missed something I don't think this can help - in our case the
content of the initramfs is changing, not just the filename due to the version.
Cheers
Paul
next prev parent reply other threads:[~2022-11-10 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 0:23 [RFC] [PATCH] Allow fitimage + initramfs rebuild to be accelerated Paul Eggleton
2022-11-09 19:41 ` [OE-core] " Paul Eggleton
2022-11-09 19:53 ` Martin Jansa
2022-11-10 20:21 ` Paul Eggleton [this message]
2022-11-09 22:14 ` Richard Purdie
2022-11-10 20:32 ` Paul Eggleton
2022-11-11 13:25 ` Rasmus Villemoes
2022-11-11 13:35 ` Richard Purdie
2022-11-11 18:13 ` Bruce Ashfield
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=3463540.iIbC2pHGDl@linc \
--to=bluelightning@bluelightning.org \
--cc=Martin.Jansa@gmail.com \
--cc=abdellatif.elkhlifi@arm.com \
--cc=andrej.valek@siemens.com \
--cc=george.mccollister@gmail.com \
--cc=liu.ming50@gmail.com \
--cc=manjukumar.harthikote-matha@xilinx.com \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=sean.anderson@seco.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