From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: mxs: tools: Add support for verbose and silent boot progress flags
Date: Thu, 9 Oct 2014 00:48:14 +0200 [thread overview]
Message-ID: <201410090048.14131.marex@denx.de> (raw)
In-Reply-To: <CA+8g9e9-JS9JJBQpDEcENmortK9og-0rXH+hp4jH-iP9ft1yaw@mail.gmail.com>
On Thursday, October 09, 2014 at 12:29:10 AM, Alexey Ignatov wrote:
> 2014-10-09 2:10 GMT+04:00 Marek Vasut <marex@denx.de>:
> > On Wednesday, October 08, 2014 at 10:49:38 PM, Alexey Ignatov wrote:
> >> mkimage -T mxs now support new flags in config file:
> >> NODISPLAYPROGRESS - makes boot silent
> >
> > Please make this the other way -- that is, add flag to make the display
> > not- silent. What does this mean anyway?
>
> Default behaviour of current MXS booting is to print HTLLCHTLLC
> characters when before usual uboot output - it is a feature to debug
> early boot stages, signatures checking, etc. Negation here to not
> break default behaviour
That's OK, you can just patch the arch/arm/cpu/arm926ejs/mxs/mxsimage*cfg to
keep the behavior intact.
> >> VERBOSEPROGRESS - makes boot progress display more verbose
> >
> > And how is the above different from this new flag?
>
> I'm not really sure what this does (I haven't seen any differences
> with this flag on and off), but
> http://www.rockbox.org/wiki/SbFileFormat mentions existence of this
> bit. Unfortunately, Freescale documentation is not full and a bit hard
> to search and use :(
Do we need this at all then ?
> > Please document those flags in doc/README.mxsimage too.
> > The code looks mostly OK, thanks !
>
> Thank you for comments, I'll add documentation, fix DISPLAYPROGRESS
> and post a v2 of the patch.
Thanks!
Best regards,
Marek Vasut
prev parent reply other threads:[~2014-10-08 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 20:49 [U-Boot] [PATCH] ARM: mxs: tools: Add support for verbose and silent boot progress flags Alexey Ignatov
2014-10-08 22:10 ` Marek Vasut
2014-10-08 22:29 ` Alexey Ignatov
2014-10-08 22:48 ` Marek Vasut [this message]
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=201410090048.14131.marex@denx.de \
--to=marex@denx.de \
--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.