From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] xilinx: disable Unicode capitalization
Date: Mon, 17 May 2021 08:39:12 +0200 [thread overview]
Message-ID: <5784507a-58e5-d6e8-3555-36c033131977@xilinx.com> (raw)
In-Reply-To: <20210516091731.26845-1-xypron.glpk@gmx.de>
On 5/16/21 11:17 AM, Heinrich Schuchardt wrote:
> Save some KiB when building xilinx_versal_virt_defconfig by disabling
> Unicode capitalization support. This avoids build failures when adding new
> features for the UEFI sub-system.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> It would be preferable to have a size check for the u-boot binary.
> This would avoid seeing problems only during execution.
> ---
> configs/xilinx_versal_virt_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configs/xilinx_versal_virt_defconfig b/configs/xilinx_versal_virt_defconfig
> index 707693713a..8bc2ff4a4c 100644
> --- a/configs/xilinx_versal_virt_defconfig
> +++ b/configs/xilinx_versal_virt_defconfig
> @@ -111,3 +111,4 @@ CONFIG_USB_GADGET_PRODUCT_NUM=0x0300
> CONFIG_USB_GADGET_DOWNLOAD=y
> CONFIG_USB_FUNCTION_THOR=y
> CONFIG_OF_LIBFDT_OVERLAY=y
> +# CONFIG_EFI_UNICODE_CAPITALIZATION is not set
> --
> 2.30.2
>
What's the build issue? Any log? U-Boot is getting bigger and bigger and
we are enabling more and more features for our generic targets that's
why fixing that problem is better than disabling some options.
Thanks,
Michal
next prev parent reply other threads:[~2021-05-17 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 9:17 [PATCH 1/1] xilinx: disable Unicode capitalization Heinrich Schuchardt
2021-05-17 6:39 ` Michal Simek [this message]
2021-05-17 8:01 ` Heinrich Schuchardt
2021-05-17 9:04 ` Stefan Roese
2021-05-17 9:37 ` Michal Simek
2021-05-17 9:40 ` Stefan Roese
2021-05-17 9:47 ` Michal Simek
2021-05-17 10:54 ` Heinrich Schuchardt
2021-05-17 11:21 ` Michal Simek
2021-05-18 4:43 ` Stefan Roese
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=5784507a-58e5-d6e8-3555-36c033131977@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.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.