From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Make U-Boot log great again
Date: Tue, 10 Jul 2018 10:38:05 -0400 [thread overview]
Message-ID: <20180710143805.GG27264@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmWYD52Fy_UPFvYMNq2BHJHypzztAzVWcyyhv3709n9mhA@mail.gmail.com>
On Tue, Jul 10, 2018 at 11:01:14AM +0800, Bin Meng wrote:
> Hello,
>
> On Fri, Mar 23, 2018 at 1:44 PM, Bin Meng <bmeng.cn@gmail.com> wrote:
> > Hi,
> >
> > On Sat, Feb 17, 2018 at 3:49 AM, Robert Nelson <robertcnelson@gmail.com> wrote:
> >> On Fri, Feb 16, 2018 at 1:01 PM, Sam Protsenko
> >> <semen.protsenko@linaro.org> wrote:
> >>> Hi guys,
> >>>
> >>> TL;DR This is a suggestion about fixing U-Boot log, which has got
> >>> worse recently.
> >>>
> >>> Right now U-Boot and SPL logs are cluttered with bogus warnings like
> >>> these (on X15 board, but I'm pretty sure it should appear on many
> >>> others):
> >>>
> >>> Loading Environment from FAT...
> >>> *** Warning - bad CRC, using default environment
> >>> Failed (-5)
> >>
> >
> > Do we plan to fix this "Failed (-5)" message? It's very confusing.
> > Like previous U-Boot just printing "*** Warning - bad CRC, using
> > default environment" is enough I think.
> >
>
> The v2018.07 release still has this "Failed (-5)" message on boot.
> When do we plan to fix this?
I don't mean for this to sound glib, but I was expecting patches to get
posted to change this particular area at least. I thought it had been
talked to the point where it was understood what the next steps should
look like? Thanks/sorry!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180710/871d3437/attachment.sig>
next prev parent reply other threads:[~2018-07-10 14:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 19:01 [U-Boot] [RFC] Make U-Boot log great again Sam Protsenko
2018-02-16 19:49 ` Robert Nelson
2018-03-23 5:44 ` Bin Meng
2018-07-10 3:01 ` Bin Meng
2018-07-10 14:38 ` Tom Rini [this message]
2018-07-11 14:51 ` Sam Protsenko
2018-07-17 22:14 ` Sam Protsenko
2018-07-18 21:41 ` Sam Protsenko
2018-02-18 21:22 ` Wolfgang Denk
2018-02-19 17:47 ` Sam Protsenko
2018-02-19 19:09 ` Wolfgang Denk
2018-02-20 8:00 ` Maxime Ripard
2018-02-20 9:59 ` Lukasz Majewski
2018-02-21 13:35 ` Tom Rini
2018-02-21 13:55 ` Maxime Ripard
2018-02-21 14:59 ` Tom Rini
2018-02-21 14:38 ` Simon Goldschmidt
2018-02-21 14:54 ` Tom Rini
2018-02-21 15:03 ` Simon Goldschmidt
2018-02-21 15:07 ` Maxime Ripard
2018-02-21 15:14 ` Tom Rini
2018-02-22 13:33 ` Maxime Ripard
2018-02-24 20:52 ` Wolfgang Denk
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=20180710143805.GG27264@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