From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org,
"\"\\\\\\\"Uwe\\\" Kleine-König\""
<u.kleine-koenig@pengutronix.de>
Subject: Re: Beaglebone white: Kernel doesn't start with barebox-2014.03.0
Date: Tue, 22 Apr 2014 12:34:13 +0200 (CEST) [thread overview]
Message-ID: <1125368747.180228.1398162853697.open-xchange@email.1und1.de> (raw)
In-Reply-To: <1398155200.5085.6.camel@weser.hi.pengutronix.de>
> Lucas Stach <l.stach@pengutronix.de> hat am 22. April 2014 um 10:26
> geschrieben:
>
>
> Am Dienstag, den 22.04.2014, 09:08 +0200 schrieb Rolf Evers-Fischer:
> > Hi Lukasz and Uwe,
> >
> > > Lucas Stach <dev@lynxeye.de> hat am 21. April 2014 um 17:24 geschrieben:
> > >
> > >
> > > Am Mittwoch, den 16.04.2014, 22:02 +0200 schrieb Uwe Kleine-König:
> > > > On Wed, Apr 16, 2014 at 05:35:52PM +0200, Lucas Stach wrote:
> > > > > Hi Rolf,
> > > > >
> > > > > Am Dienstag, den 15.04.2014, 13:28 +0200 schrieb Rolf Evers-Fischer:
> > > > > > Dear all,
> > > > > > after update to barebox-2014.03.0, the kernel on my beaglebone-white
> > > > > > doesn't
> > > > > > start anymore.
> > > > > > The last line, which appears, is "booting kernel with devicetree".
> > > > > > I discovered that the problem is caused by the commit [1]. When I
> > > > > > revert
> > > > > > this
> > > > > > commit, everything works fine.
> [...]
> > >
> > Thank you for your suggestions.
> > If you don't mind, I'll wait for another patch and try booting a zImage
> > (with
> > and without the upcoming patch).
> >
> Could you please test the patch first? I'll come up with a complete
> series to fix some more issues I've spotted here, but I would like to
> know if this approach is ok to fix the issue on BeagleBone white.
>
No problem.
First I've used zImage (instead of uImage) without your patch: The kernel
started.
Additionally I've applied your patch: The kernel started as well.
Now I tried the suggested change from Uwe(*): The kernel started as well.
So, it seems that your patch doesn't break the kernel start.
Best regards,
Rolf
(*) I assume that I had to use 'header->start' instead of the unknown parameter
'start'.
Otherwise I was not able to compile the barebox.
> Thanks,
> Lucas
>
> --
> Pengutronix e.K. | Lucas Stach |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-04-22 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 11:28 Rolf Evers-Fischer
2014-04-16 15:35 ` Lucas Stach
2014-04-16 20:02 ` Uwe Kleine-König
2014-04-21 15:24 ` Lucas Stach
2014-04-22 7:08 ` Rolf Evers-Fischer
2014-04-22 8:26 ` Lucas Stach
2014-04-22 10:34 ` Rolf Evers-Fischer [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=1125368747.180228.1398162853697.open-xchange@email.1und1.de \
--to=embedded24@evers-fischer.de \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.de \
--cc=u.kleine-koenig@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox