From: Tom Rini <trini@konsulko.com>
To: Caleb Connolly <caleb.connolly@linaro.org>
Cc: E Shattow <lucent@gmail.com>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
u-boot@lists.denx.de, linux-amarula@amarulasolutions.com,
Eddie James <eajames@linux.ibm.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 1/2] bootm: adjust the print format
Date: Mon, 26 Aug 2024 09:01:46 -0600 [thread overview]
Message-ID: <20240826150146.GG2479150@bill-the-cat> (raw)
In-Reply-To: <7a25850c-6082-4490-867b-126b480ba757@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2868 bytes --]
On Mon, Aug 26, 2024 at 02:26:10PM +0100, Caleb Connolly wrote:
>
>
> On 25/08/2024 19:36, E Shattow wrote:
> > On Sun, Aug 25, 2024 at 5:26 AM Dario Binacchi
> > <dario.binacchi@amarulasolutions.com> wrote:
> > >
> > > All three addresses printed are in hexadecimal format, but only the
> > > first two have the "0x" prefix. The patch aligns the format of the
> > > "end" address with the other two by adding the "0x" prefix.
> > >
> > > Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> > > ---
> > >
> > > boot/bootm.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/boot/bootm.c b/boot/bootm.c
> > > index 480f8e6a0e6e..951e549f19ff 100644
> > > --- a/boot/bootm.c
> > > +++ b/boot/bootm.c
> > > @@ -703,7 +703,7 @@ static int bootm_load_os(struct bootm_headers *images, int boot_progress)
> > >
> > > /* Handle BOOTM_STATE_LOADOS */
> > > if (relocated_addr != load) {
> > > - printf("Moving Image from 0x%lx to 0x%lx, end=%lx\n",
> > > + printf("Moving Image from 0x%lx to 0x%lx, end=0x%lx\n",
> > > load, relocated_addr,
> > > relocated_addr + image_size);
> > > memmove((void *)relocated_addr, load_buf, image_size);
> > > --
> > > 2.43.0
> > >
> >
> > From U-Boot documentation, alpha-numeric input is assumed to be
> > hexadecimal except when it is not, and generally does not accept "0x"
> > prefix on input. So the correct action would be to make this
While there was some point in history where I'm sure we got confused by
"0x" input I don't think that's true anymore (and everything should be
using some strto function that works as expected, not a custom parser).
So the docs should be updated there.
> > consistent over the whole U-Boot code base, or remove the "0x"
> > prefixes (not add more of them) ?
>
> Most(?) U-Boot commands accept the 0x prefix. I don't think stripping it is
> sensible, I myself have gotten confused many times over hex values that lack
> the leading 0x in U-Boot output.
>
> Maybe unavailable in SPL (not sure) but I prefer the "%#lx" format which
> prepends the 0x automatically.
That we assume input is hex is just what it is these days. Output really
ought to be prefixed with 0x because that's just common convention (and
whatever we assumed people would Just Know 25+ years ago may not be true
today). Since updating this output really shouldn't change our ABI, it's
conceptually fine with me but we don't use "%#lx" a lot and so I don't
know if tiny-printf handles it and so that might not be the right call
for SPL code and so lets not change this patch.
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-08-26 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 12:26 [PATCH 1/2] bootm: adjust the print format Dario Binacchi
2024-08-25 12:26 ` [PATCH 2/2] cmd: booti: " Dario Binacchi
2024-08-29 14:05 ` Simon Glass
2024-08-29 14:25 ` Dario Binacchi
2024-08-29 15:00 ` Simon Glass
2024-08-29 15:03 ` Tom Rini
2024-08-30 0:58 ` Simon Glass
2024-08-25 18:36 ` [PATCH 1/2] bootm: " E Shattow
2024-08-26 13:26 ` Caleb Connolly
2024-08-26 15:01 ` Tom Rini [this message]
2024-09-26 16:56 ` Dario Binacchi
2024-08-26 17:49 ` Simon Glass
2024-08-26 6:34 ` Mattijs Korpershoek
2024-10-03 2:52 ` 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=20240826150146.GG2479150@bill-the-cat \
--to=trini@konsulko.com \
--cc=caleb.connolly@linaro.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=eajames@linux.ibm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=lucent@gmail.com \
--cc=mkorpershoek@baylibre.com \
--cc=sjg@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).