Le 01/03/2012 10:44, Alexander Graf a écrit :
On 01.03.2012, at 09:04, Jason Kridner wrote:
On Wed, Feb 29, 2012 at 16:32, Alexander Graf <agraf@suse.de> wrote:
Still need to figure out what exactly is going wrong there. But it's definitely the MLO code that's broken, not the boot rom. Wondering why we could'nt move to denx.com u-boot SPL instead of using x-loader MLO? +1. SPL is the right choice today. Nishanth did a great job
On Wed, Feb 29, 2012 at 5:56 PM, Menon, Nishanth <nm@ti.com> wrote: maintaining x-loader, but it was always a fork of u-boot and with SPL we've eliminated that fork. Thanks Nishanth for highlighting this. Yeah, good point. We already use SPL for the Panda, but somehow didn't manage to get the OMAP3 x-loader also based on it. I honestly don't remember why.
Just tried to compile u-boot with SPL and it is 329K which is greater than the 128K limit for beagleboard (OMAP3/DM37x). So we have to use MLO+u-boot.
But given the new issues, we probably should give it another try :). I'll try to hack on this in a spare minute. Or if anyone else wants to pick it up, please check the u-boot-omap4panda package in openSUSE:Factory:ARM on how it's done for OMAP4 :).
Alex
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org