From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de, trini@konsulko.com, sjg@chromium.org
Subject: Re: [PATCH 6/7] efi_loader: disk: compile efi_disk when CONFIG_BLK
Date: Thu, 21 Apr 2022 09:30:55 +0900 [thread overview]
Message-ID: <20220421003055.GA7584@laputa> (raw)
In-Reply-To: <238f2357-34da-eca0-071d-7cec914fabda@gmx.de>
On Wed, Apr 20, 2022 at 09:42:00AM +0200, Heinrich Schuchardt wrote:
> On 4/19/22 03:01, AKASHI Takahiro wrote:
> > Now we can build efi_loader with block device support (CONFIG_BLK) and
> > without CONFIG_PARTITIONS.
> > So change Makefile.
> >
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > ---
> > lib/efi_loader/Makefile | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/efi_loader/Makefile b/lib/efi_loader/Makefile
> > index 034d26cf0109..aaaa25cefe01 100644
> > --- a/lib/efi_loader/Makefile
> > +++ b/lib/efi_loader/Makefile
> > @@ -68,7 +68,7 @@ obj-y += efi_watchdog.o
> > obj-$(CONFIG_EFI_ESRT) += efi_esrt.o
> > obj-$(CONFIG_LCD) += efi_gop.o
> > obj-$(CONFIG_DM_VIDEO) += efi_gop.o
> > -obj-$(CONFIG_PARTITIONS) += efi_disk.o
> > +obj-$(CONFIG_BLK) += efi_disk.o
>
> Why do we need efi_disk.o if CONFIG_PARTITIONS=n?
Why do you think so?
As you admitted in your comment at:
https://lists.denx.de/pipermail/u-boot/2022-April/481546.html
GPT(EFI_PARTITION) is optional under the current implementation
("EFI_LOADER should imply EFI_PARTITION" in your words).
As a matter of fact, EFI_LOADER (and efi_disk.o) can be compiled in
even without any partition table types.
If you don't agree, please drop this patch.
I don't care because it won't help reducing SPL code size anyway.
-Takahiro Akashi
> How can we be UEFI compliant without partition support?
>
> Best regards
>
> Heinrich
>
> > obj-$(CONFIG_NET) += efi_net.o
> > obj-$(CONFIG_GENERATE_ACPI_TABLE) += efi_acpi.o
> > obj-$(CONFIG_GENERATE_SMBIOS_TABLE) += efi_smbios.o
>
next prev parent reply other threads:[~2022-04-21 0:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 1:01 [PATCH 0/7] disk: don't compile in partition support for spl/tpl if not really necessary AKASHI Takahiro
2022-04-19 1:01 ` [PATCH 1/7] disk: include errno.h explicitly in part.h AKASHI Takahiro
2022-04-19 1:01 ` [PATCH 2/7] disk: enable function prototypes in part.h for SPL/TPL AKASHI Takahiro
2022-04-19 1:01 ` [PATCH 3/7] disk: define nullified functions for !PARTITIONS AKASHI Takahiro
2022-04-19 3:09 ` Tom Rini
2022-04-19 4:11 ` AKASHI Takahiro
2022-04-19 12:12 ` Tom Rini
2022-04-20 2:17 ` AKASHI Takahiro
2022-04-20 2:50 ` Tom Rini
2022-04-19 1:01 ` [PATCH 4/7] sandbox: move a function prototype AKASHI Takahiro
2022-04-19 1:01 ` [PATCH 5/7] efi_loader: PARTITION_UUIDS should be optional AKASHI Takahiro
2022-04-20 7:37 ` Heinrich Schuchardt
2022-04-21 0:57 ` AKASHI Takahiro
2022-04-21 13:13 ` Tom Rini
2022-04-19 1:01 ` [PATCH 6/7] efi_loader: disk: compile efi_disk when CONFIG_BLK AKASHI Takahiro
2022-04-20 7:42 ` Heinrich Schuchardt
2022-04-21 0:30 ` AKASHI Takahiro [this message]
2022-04-23 20:08 ` Heinrich Schuchardt
2022-04-19 1:01 ` [PATCH 7/7] disk: don't compile in partition support for spl/tpl if not really necessary AKASHI Takahiro
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=20220421003055.GA7584@laputa \
--to=takahiro.akashi@linaro.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.