On 2/3/20 6:48 PM, LABBE Corentin wrote: > On Wed, Jan 29, 2020 at 07:21:09AM +0900, Jaehoon Chung wrote: >> On 1/27/20 9:06 PM, Andre Przywara wrote: >>> On Mon, 27 Jan 2020 12:50:16 +0100 >>> LABBE Corentin <cla...@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. >> > > Hello > > I have searched both in uboot and linux sources and didnt found any > CONFIG_ARCH_FIXUP_OF_MEMORY.
Sorry. It's CONFIG_ARCH_FIXUP_FDT_MEMORY. Best Regards, Jaehoon Chung > Could you give what you did exactly ? > > Regards > >
