On Tue, Feb 28, 2017 at 07:59:47AM +0100, Sascha Hauer wrote: > On Sat, Feb 25, 2017 at 09:52:38PM +0100, Uwe Kleine-König wrote: > > Hello, > > > > one specialty of mvebu is that it has a movable register window. Its > > base address is configured within this register range, so there is no > > way to find out the current position. The BootROM leaves this window at > > 0xd0000000, however it is beneficial to move it further to the end of > > the address range (usually 0xf1000000) to benefit from more continuous > > RAM. For this reason one of the first things that barebox does it to > > move the window accordingly. If however barebox is loaded as a second > > stage image this results in a crash as the register base address > > register is already moved. > > > > This series implements that the called image gets the base address from > > the barebox header. It defaults to 0xd0000000 which is right for the > > (unaware) BootROM and when barebox jumps into such an image the register > > position is passed accordingly. > > This makes the 2nd stage images unnecessary, right? Can you remove them > from images/Makefile.mvebu? I thought about that already, too, but they are still necessary when you convert from U-Boot to barebox or upgrade from an older barebox. So I think keeping them for now makes sense. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
