[PATCH u-boot 11/12] bootm: fix ramdisk relocation
Cédric Le Goater
clg at kaod.org
Mon Oct 10 18:41:34 AEDT 2016
On 10/10/2016 08:23 AM, Joel Stanley wrote:
> On Fri, Oct 7, 2016 at 8:26 AM, Cédric Le Goater <clg at kaod.org> wrote:
>> We are working on bringing to mainline a set of changes adding support
>> for the Aspeed SoC and we have a couple of work around we are trying
>> to elimitate first. This is one of them. The ramdisk is not relocated
>> and Linux fails to boot. The current port does not use a device tree
>> (yet) so that might be the most obvious culprit.
>>
>> Thanks
>>
>> Signed-off-by: Cédric Le Goater <clg at kaod.org>
>
> I see you're chatting with upstream about this one.
>
> Do you want me to include this in our tree for now, or wait for the
> outcome of those discussions?
Let's wait. The current hack does exactly what Linux needs, which
is to load the ramdisk at the load address of the ramdisk image.
This patch enables loading but on some occasion, the ramdisk can be
loaded in conflicting memblocks for Linux, which then disables
INITRD ... So we need to do better than that.
C.
More information about the openbmc
mailing list