[U-Boot] Help: U-Boot on Nokia RX-51 (aka N900)

Marek Vasut
2011-09-01T09:39:58Z

On Thursday, September 01, 2011 11:06:51 AM Pali Roh?r wrote:
> On Thursday 01 September 2011 10:46:38 Marek Vasut wrote:
> > On Thursday, September 01, 2011 10:42:48 AM Pali Roh?r wrote:
> > > Hello,
> > >
> > > U-Boot patches which add support for Nokia RX-51 (aka N900) is here:
> > > http://al.robotfuzz.com/~al/maemo/u-boot/
> > >
> > > RX-51 has closed 2nd stage bootloader NOLO which can load kernel image
> > > from nand (or usb) to ram and boot it. NOLO also done all HW
> > > initializations. These U-Boot patches for RX-51 add support that
> > > builded U-Boot binary can be loaded and booted by NOLO. So U-Boot will
> > > be 3rd bootloader.
> > >
> > > Patches are on top of revision bd2313078114c4b44c4a5ce149af43bcb7fc8854
> > > and working fine. I rebased these patches on top of u-boot git master
> > > repository, but booting failed. No output on device. Using git bisect I
> > > found that problem appeared at revision
> > >
> > > 561142af20f1fd7b425d9425730014e656defb91
> > > ARM: implement relocation for ARM V7 (OMAP)
> > >
> > > If I defined CONFIG_SYS_ARM_WITHOUT_RELOC U-Boot working and booting
> > > fine
> > > up to revision a9aa3926295df759306258e5e24cace414f53b67
> > >
> > > So problem is that relocation patches broke RX-51 support. Can somebody
> > > help me how to rewrite/port rx-51 patches to work with ARM relocation
> > > (do
> > > not forget that U-Boot is loaded by 2nd bootloader to RAM after HW is
> > > initialized by NOLO)? If U-Boot will be working on RX-51 I will prepair
> > > patches for upstreaming.
> >
> > Does NOLO enable MMU ?
>
> I'm not sure, because NOLO is proprietary, closed and without any
> documentation. Nobody knows what all NOLO doing...

Check CPSR

>
> > btw can you post the patches to the ML for review ?
>
> 4 patches on http://al.robotfuzz.com/~al/maemo/u-boot/ is not mine and is
> not ready for merging - but working.
>
> I'm prepairing patch series which fix some problems (keymap, watchog, ...).
> Now it is still based on bd2313078114c4b44c4a5ce149af43bcb7fc8854

Well ok.

>
> > Cheers