All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv2 1/3] igep00x0: disable CONFIG_DISPLAY_BOARDINFO
Date: Fri, 4 Nov 2016 18:21:49 +0100	[thread overview]
Message-ID: <20161104172149.GA898@localhost.localdomain> (raw)
In-Reply-To: <ef3936d3-3967-bc71-4fdc-7a78b12a3c45@osg.samsung.com>

On Fri, Nov 04, 2016 at 12:42:57PM -0300, Javier Martinez Canillas wrote:
> Hello Ladis,
> 
> On 11/04/2016 08:55 AM, Ladislav Michl wrote:
> > As a single U-Boot binary can now run on various board modifications,
> > drop CONFIG_DISPLAY_BOARDINFO as it prints flash memory information
> > too early to give us chance to easily detect it. Also saves few bytes
> > as a bonus.
> > 
> > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > ---
> 
> I tried to test your patches on latest u-boot master (sha-1 dd93a8e9e688)
> but my IGEPv2 board fails to boot and prints in an infinite loop following:
> 
> "ecc unrecoverable error"

This comes from SPL, right? That would imply you boot from NAND...

> This is not related to your patches though, since I've the same issue
> without your patches applied.
> 
> Did you see this issue? u-boot works with previous v2016.09 release so
> this is a newly introduced regression.

No, otherwise I would fix that. Care to send complete boot log if there is
any?

> Unfortunately I don't have time to dig deeper on this but I may give a
> try next week.

Thank you,
	ladis

  parent reply	other threads:[~2016-11-04 17:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20  9:04 [U-Boot] [PATCH 1/3] igep00x0: disable CONFIG_DISPLAY_BOARDINFO Ladislav Michl
2016-09-20  9:07 ` [U-Boot] [PATCH 2/3] igep00x0: consolidate defconfigs Ladislav Michl
2016-09-20 12:52   ` Tom Rini
2016-09-20 22:44     ` Ladislav Michl
2016-09-20 23:45       ` Tom Rini
2016-09-20 23:52         ` Ladislav Michl
2016-09-21  0:26           ` Tom Rini
2016-09-21  9:39             ` Ladislav Michl
2016-09-21 11:46               ` Enric Balletbo Serra
2016-09-21 12:51                 ` Tom Rini
2016-09-21 13:46                   ` Enric Balletbo Serra
2016-09-21 14:02                     ` Tom Rini
2016-09-22  5:12                       ` Ladislav Michl
2016-09-20  9:09 ` [U-Boot] [PATCH 3/3] igep00x0: add Hynix timings Ladislav Michl
2016-09-20 15:41 ` [U-Boot] [PATCH 1/3] igep00x0: disable CONFIG_DISPLAY_BOARDINFO Enric Balletbo Serra
2016-09-20 23:10   ` Ladislav Michl
2016-11-04 11:47   ` Ladislav Michl
2016-11-04 11:55     ` [U-Boot] [PATCHv2 " Ladislav Michl
     [not found]       ` <ef3936d3-3967-bc71-4fdc-7a78b12a3c45@osg.samsung.com>
2016-11-04 17:21         ` Ladislav Michl [this message]
2016-11-04 19:34           ` Javier Martinez Canillas
2016-11-04 19:36       ` Javier Martinez Canillas
2016-11-13 20:58       ` [U-Boot] [U-Boot, PATCHv2, " Tom Rini
2016-11-04 11:57     ` [U-Boot] [PATCHv2 2/3] igep00x0: consolidate defconfigs Ladislav Michl
2016-11-04 19:37       ` Javier Martinez Canillas
2016-11-13 20:58       ` [U-Boot] [U-Boot,PATCHv2,2/3] " Tom Rini
2016-11-04 11:59     ` [U-Boot] [PATCHv2 3/3] igep00x0: add Hynix timings Ladislav Michl
2016-11-04 19:39       ` Javier Martinez Canillas
2016-11-13 20:58       ` [U-Boot] [U-Boot,PATCHv2,3/3] " 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=20161104172149.GA898@localhost.localdomain \
    --to=ladis@linux-mips.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 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.