[PATCH v3 0/3] Ethernet support for Raspberry Pi 4

[Jaehoon Chung]

On 1/27/20 9:06 PM, Andre Przywara wrote:
> On Mon, 27 Jan 2020 12:50:16 +0100
> LABBE Corentin <clabbe at baylibre.com> wrote:
> 
> Hi,
> 
>> On Mon, Jan 27, 2020 at 04:27:03PM +0530, Amit Tomer wrote:
>>> Hi,
>>>   
>>>> The kernel panic just after with "OF: reserved mem: failed to allocate memory for node 'linux,cma'" but that's another story.  
>>>
>>> But this comes even without having Ethernet patches and when one use
>>> booti instead of bootefi, right ?
>>>   
>>
>> So booti is unsupported on rpi 4 ?
> 
> It should be supported, but apparently there is some bug. I guess it's about not properly reserving memory used by the armstub/ATF. Do you use the embedded RPi foundation armstub or ATF (do you have an "armstub=..." line in config.txt)?
> 
> I will try take a look at this later.

I'm not sure, i had similar issue about failed to allocate memory cma.
I had enabled CONFIG_ARCH_FIXUP_OF_MEMORY. And i changed the loading address (kernel/ramdisk/device-tree) in boot script for our environment.
Because sometime some address range is overwritten.

Best Regards,
Jaehoon Chung

> 
>> I need to set a ramdisk and bootefi dont support that.
> 
> Try "initrd=<filename>" on the kernel command line.
> This is actually an EFI stub feature, the EFI command line is parsed by this pre-kernel code, which filters for initrd= and loads the initrd using the UEFI API (implemented by U-Boot).
> So the initrd has to live on the EFI system partition, which means you can't load it easily via TFTP :-(
> More details here: https://www.kernel.org/doc/html/latest/admin-guide/efi-stub.html#the-initrd-option
> 
> Cheers,
> Andre
> 
>