From: Sascha Hauer <s.hauer@pengutronix.de>
To: anis chali <chalianis1@gmail.com>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH 6/7] efi: payload: add support for efi stub boot and fit image.
Date: Thu, 4 Sep 2025 08:48:25 +0200 [thread overview]
Message-ID: <aLk2OXrt357LdhkT@pengutronix.de> (raw)
In-Reply-To: <CAL+1fyA5FtjLfRDbF-dpxr=T6kL=hrF8pr6wJk5aR1X=5CEFUg@mail.gmail.com>
On Thu, Sep 04, 2025 at 02:20:59AM -0400, anis chali wrote:
> Hi Sascha,
> > Please keep the list on Cc. Other people might be interested as well and
> > might have some opinion in the discussions taking place.
> Sorry for that of course.
> > I just looked around how fit_has_image() is used. The return value is
> > treated as bool by all callers, so I think it's better to just return
> > bool from the function. I just sent a patch for it...
> ack
> > Sorry, I don't understand the question.
> I was asking, would 128KB be always enough to cover any hardware, should
> we go for 512KB instead?
When I understand correctly the 128KiB would only be the additional
memory for later additions to the device tree, right?
I think for that 128KiB should be quite much already.
> For now I submitted with 128KB.
> > No. I don't do EFI very much and I currently don't have a setup for
> > testing this. Ahmad is more experienced with EFI than me.
> Ok, I can maybe share my scripts, they are not clean at all with many
> repos. if I have time
> I will do some clean up and share them (there scripts to generate
> fitImage, linux, dts, optee, TF-A, UKI, edk2, custom qemu ...).
> Thanks.
Great, looking forward to it.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-09-04 6:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 3:55 [PATCH 1/7] drivers: video: efi-gop: fix null reference pointer chalianis1
2025-08-31 3:55 ` [PATCH 2/7] efi: video: gop: remove dependency to x86 chalianis1
2025-09-02 9:20 ` Ahmad Fatoum
2025-08-31 3:55 ` [PATCH 3/7] efi: payload: initrd: implement efi initrd media protocol chalianis1
2025-08-31 3:55 ` [PATCH 4/7] arm: efi: add a generic efi machine chalianis1
2025-09-03 7:14 ` Sascha Hauer
2025-09-04 8:20 ` Ahmad Fatoum
2025-09-05 0:16 ` anis chali
2025-09-05 19:04 ` Ahmad Fatoum
2025-08-31 3:55 ` [PATCH 5/7] lib: fdt: add lib fdt padding size chalianis1
2025-08-31 3:55 ` [PATCH 6/7] efi: payload: add support for efi stub boot and fit image chalianis1
2025-09-03 7:11 ` Sascha Hauer
[not found] ` <CAL+1fyD6Jevxx_wP00caRoXe0yRmM6uScJN8W3fkRVNVfLRj1Q@mail.gmail.com>
[not found] ` <aLksEfZ3-YiEL-xN@pengutronix.de>
[not found] ` <CAL+1fyA5FtjLfRDbF-dpxr=T6kL=hrF8pr6wJk5aR1X=5CEFUg@mail.gmail.com>
2025-09-04 6:48 ` Sascha Hauer [this message]
2025-09-04 6:55 ` Ahmad Fatoum
2025-09-04 9:03 ` Ahmad Fatoum
2025-09-04 22:44 ` anis chali
2025-09-05 19:10 ` Ahmad Fatoum
2025-09-05 19:24 ` Ahmad Fatoum
2025-08-31 3:55 ` [PATCH 7/7] efi: payload: add options for FDT force and initrd direct install chalianis1
2025-09-04 9:19 ` Ahmad Fatoum
2025-09-04 22:30 ` anis chali
2025-09-05 19:18 ` Ahmad Fatoum
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=aLk2OXrt357LdhkT@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=chalianis1@gmail.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 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.