From: Cristiano Rodrigues <microcris@sapo.pt>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: Re: barebox-2013.07/08.0 works from RAM but fails from NAND (Mini2440)
Date: Thu, 08 Aug 2013 16:05:50 +0100 [thread overview]
Message-ID: <2914196.CyBYm9GnKj@probook> (raw)
In-Reply-To: <1375973567.984569011@f351.i.mail.ru>
On Thursday 08 August 2013 18:52:47 Alexander Shiyan wrote:
> > 2013/8/8 Pawel Suchanecki <pawel.suchanecki@gmail.com>:
> > > Dear list & developers,
> > >
> > > My barebox works (I get barebox prompt and can boot from there) when
> > > loaded
Hi there :)
It is the first commit after the barebox version 2013.05.1 that is breaking
the mini2440 NAND boot.
cris@ProBook:~/mini2440/Boot/barebox_git$ git bisect bad
5f82a0cd0138ae5208cc8758c638ce6a928ed2e3 is the first bad commit
commit 5f82a0cd0138ae5208cc8758c638ce6a928ed2e3
Author: Alexander Shiyan <shc_work@mail.ru>
Date: Tue Apr 9 19:05:31 2013 +0400
ARM: cpuimx51: Use custom padctrl for fec
The fec padctrl is different from what we have in the kernel iomux
file. To be able to keep the iomux file in sync with the kernel, use
a custom padctrl for the cpuimx51 board.
Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
:040000 040000 7196169700f35cef11d849e562784591874f770d
7a4888609304c2de992b22da06ad206189dde06b M arch
> > > to ram by (super)vivi but does not when I flash it to NAND.
> > >
> > > Barebox does not output anything to the console. It also fails using
> > > "friendlyarm_mini2440_defconfig". It behaves the same in 2013.07.0 and
> > > 2013.08.0.
> > >
> > > Please direct me: where can I look for the misconfiguration? What did I
> > > do
> > > wrong?
> > >
> > > Thanks,
> > > Pawel.
> >
> > Hi again,
> >
> > I found the thread in which Cristiano already reported such behaviour,
> > namely: http://article.gmane.org/gmane.comp.boot-loaders.barebox/10142
> >
> > Seems I am in same situation. Barebox.2013.05.1 starts from NAND.
>
> The easy way to resolve this issue is "git bisect".
> Can you try to do it?
>
> ---
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-08-08 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACbe1rvwSV-XvG3nhZ5eWcO_OpBpBn7QgCLMkW+-=5uATjm0+g@mail.gmail.com>
2013-08-08 14:49 ` Pawel Suchanecki
2013-08-08 14:52 ` Alexander Shiyan
2013-08-08 15:05 ` Cristiano Rodrigues [this message]
2013-08-08 16:24 ` Alexander Shiyan
[not found] ` <12401367.oRAUbcxG7q@probook>
[not found] ` <1375980427.338104700@f146.i.mail.ru>
2013-08-08 16:11 ` Cristiano Rodrigues
2013-08-08 17:15 ` Cristiano Rodrigues
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=2914196.CyBYm9GnKj@probook \
--to=microcris@sapo.pt \
--cc=barebox@lists.infradead.org \
--cc=shc_work@mail.ru \
/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