From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: 2013.05 breaking Linux boot on imx28 CFA-10036
Date: Thu, 23 May 2013 15:05:20 +0200 [thread overview]
Message-ID: <20130523130520.GG8595@lukather> (raw)
In-Reply-To: <20130523125200.GE8595@lukather>
On Thu, May 23, 2013 at 02:52:00PM +0200, Maxime Ripard wrote:
> Hi Jan,
>
> On Thu, May 23, 2013 at 12:44:16PM +0200, Jan Lübbe wrote:
> > On Thu, 2013-05-23 at 11:46 +0200, Maxime Ripard wrote:
> > > I've tested lately both 2013.05.0 and the master of Barebox on the imx28
> > > cfa-10036 board we have.
> > >
> > > Everything works fine with 2013.04.0.
> > >
> > > The issue I have is that Barebox in itself works fine, however, Linux
> > > fails to boot after it has been started by Barebox, quite early and
> > > badly:
> > >
> > > http://code.bulix.org/s3z010-83581
> >
> > Could you try the not-yet-released stable branch?
> > http://git.pengutronix.de/?p=barebox.git;a=shortlog;h=refs/heads/stable/v2013.05
>
> Hmm, I somehow overlooked that branch.
> It works now, thanks!
And just for the record, this issue is fixed with the commit 9c56cbb6.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-05-23 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 9:46 2013.05 breaking Linux boot on imx28 CFA-10036 Maxime Ripard
2013-05-23 10:44 ` Jan Lübbe
2013-05-23 12:52 ` Maxime Ripard
2013-05-23 13:05 ` Maxime Ripard [this message]
2013-05-23 13:16 ` Sascha Hauer
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=20130523130520.GG8595@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=barebox@lists.infradead.org \
--cc=jlu@pengutronix.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.