From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 3/3] lib: Allow hexdump to be used in SPL
Date: Fri, 15 May 2020 14:17:31 -0400 [thread overview]
Message-ID: <20200515181731.GA17253@bill-the-cat> (raw)
In-Reply-To: <20200506140357.32050-3-sjg@chromium.org>
On Wed, May 06, 2020 at 08:03:57AM -0600, Simon Glass wrote:
> It is sometimes useful to output hex dumps in SPL. Add a config option to
> allow this.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Stefan Roese <sr@denx.de>
> ---
>
> lib/Kconfig | 6 ++++++
> lib/Makefile | 2 +-
> 2 files changed, 7 insertions(+), 1 deletion(-)
This breaks some platforms such as:
arm: + am335x_evm
+(am335x_evm) arm-linux-gnueabi-ld.bfd: lib/built-in.o: in function `efi_set_variable_common':
+(am335x_evm) lib/efi_loader/efi_variable.c:1077: undefined reference to `hex_asc'
+(am335x_evm) arm-linux-gnueabi-ld.bfd: lib/built-in.o: in function `vsnprintf_internal':
+(am335x_evm) lib/vsprintf.c:697: undefined reference to `hex_asc'
+(am335x_evm) make[1]: *** [u-boot] Error 1
+(am335x_evm) make: *** [sub-make] Error 2
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200515/c1a20e16/attachment.sig>
next prev parent reply other threads:[~2020-05-15 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 14:03 [PATCH 1/3] log: Allow LOG_DEBUG to always enable log output Simon Glass
2020-05-06 14:03 ` [PATCH 2/3] lib: Allow MD5 to be enabled in SPL Simon Glass
2020-05-15 20:53 ` Tom Rini
2020-05-06 14:03 ` [PATCH 3/3] lib: Allow hexdump to be used " Simon Glass
2020-05-06 15:11 ` Stefan Roese
2020-05-15 18:17 ` Tom Rini [this message]
2020-05-15 18:47 ` [PATCH 1/3] log: Allow LOG_DEBUG to always enable log output Tom Rini
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=20200515181731.GA17253@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox