From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Brugger Date: Wed, 29 Jan 2020 09:04:56 +0100 Subject: [PATCH v3 0/3] Ethernet support for Raspberry Pi 4 In-Reply-To: <3c107710-5617-5a7a-d783-d6c6dc8f9037@samsung.com> References: <20200127011444.8114-1-andre.przywara@arm.com> <20200127100949.GA14303@Red> <20200127115016.GA4896@Red> <20200127120616.73342ed4@donnerap.cambridge.arm.com> <3c107710-5617-5a7a-d783-d6c6dc8f9037@samsung.com> Message-ID: <77233725-a362-2fe1-e40e-bca196204be5@suse.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 28/01/2020 23:21, Jaehoon Chung wrote: > On 1/27/20 9:06 PM, Andre Przywara wrote: >> On Mon, 27 Jan 2020 12:50:16 +0100 >> LABBE Corentin 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. > Can you share some more details? Might it make sense to change the memory addresses in include/configs/rpi.h so that it work out-of-the-box for all cases? Regards, Matthias