Beaglebone white: Kernel doesn't start with barebox-2014.03.0

[Rolf Evers-Fischer]

> Lucas Stach <l.stach at 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 at 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/ |
>