Le 28/01/2014 15:35, Guillaume Gardet a écrit :
> Le 28/01/2014 10:47, Andreas Färber a écrit :
>> Am 27.01.2014 13:53, schrieb Guillaume Gardet:
>>> Le 27/01/2014 13:16, Alexander Graf a écrit :
>>>> On 27.01.2014, at 13:06, Andreas Färber <afaer...@suse.de> wrote:
>>>>
>>>>> https://build.opensuse.org/request/show/215263
>>>>>
>>>>> If you can clean up the patch and restore the build so that we can get
>>>>> it submitted into Factory, I'll be happy.
>>>> Sorry, I won't get around to anything except for KVM and QEMU patches for 
>>>> the next few days. I'm moving houses tomorrow and will try to squeeze in 
>>>> as many patch reviews as I can in between so that I don't miss the next 
>>>> merge window.
>>>>
>>>> Guillaume, do you have some spare time atm?
>>> Not much time ATM. What is needed here?
>> https://build.opensuse.org/package/show/Base:System/u-boot-am335xevm
>>
>> This is failing with the mlo-ext2.patch (that Alex, Dirk and you all
>> have rebased in the past), now leading to an SPL too large for SRAM.
>>
>> As mentioned earlier, I was able to get that down to 104 bytes by
>> avoiding a duplicate variable assignment:
>>
>> [  390s] ld.bfd: u-boot-spl section `.u_boot_list' will not fit in
>> region `.sram'
>> [  390s] ld.bfd: region `.sram' overflowed by 104 bytes
>>
>> What's needed is to change the patch in whatever way necessary to get
>> the SPL code size small enough. Alex' suggestion was to replace FAT
>> support with ext support instead of just adding the latter.
> Good idea.
> We could also disable CONFIG_SPL_OS_BOOT since we do not boot Linux directly.
> I will give a try.

Fixed that way. See SR #215393:
https://build.opensuse.org/request/show/215393

No time to clean-up mlo-ext2.patch.

Guillaume

>
>> A lesser priority once our build is fixed would be to overhaul the patch
>> in such a way that some CONFIG_SPL_EXT_SUPPORT is used rather than
>> reusing CONFIG_SPL_FAT_SUPPORT and mentions of hacks for OMAP4 be
>> dropped, so that this can be submitted upstream and dropped as patch
>> with the next U-Boot update. Even the environment changes (fatload vs.
>> ext2load or load) could be upstreamed that way.
> I agree. We should upstream all our patches when possible.
> But this patch is not upstreamable without a big clean-up. ;)
>
>
> Guillaume
>
>> Andreas
>>

-- 
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org

Reply via email to