public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: LABBE Corentin <clabbe@baylibre.com>
To: u-boot@lists.denx.de
Subject: [PATCH v3 0/3] Ethernet support for Raspberry Pi 4
Date: Mon, 3 Feb 2020 10:50:07 +0100	[thread overview]
Message-ID: <20200203095007.GB4164@Red> (raw)
In-Reply-To: <20200127120616.73342ed4@donnerap.cambridge.arm.com>

On Mon, Jan 27, 2020 at 12:06:16PM +0000, Andre Przywara wrote:
> On Mon, 27 Jan 2020 12:50:16 +0100
> LABBE Corentin <clabbe@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 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

Just for more information, the official kernel from rpi also panic when booted with booti.
[    0.000000] Linux version 4.19.80 (oe-user at oe-host) (gcc version 8.2.0 (GCC)) #1 SMP PREEMPT Mon Jan 13 16:34:20 UTC 2020
[    0.000000] Machine model: Raspberry Pi 4 Model B
[    0.000000] earlycon: uart0 at MMIO32 0x00000000fe215040 (options '')
[    0.000000] bootconsole [uart0] enabled
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Failed to reserve 8 MiB
[    0.000000] Kernel panic - not syncing: ERROR: Failed to allocate 0x0000000000001000 bytes below 0x0000000000000000.

Regards

      parent reply	other threads:[~2020-02-03  9:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27  1:14 [PATCH v3 0/3] Ethernet support for Raspberry Pi 4 Andre Przywara
2020-01-27  1:14 ` [PATCH v3 1/3] net: Add support for Broadcom GENETv5 Ethernet controller Andre Przywara
2020-01-27  1:14 ` [PATCH v3 2/3] rpi4: Update memory map to accommodate scb devices Andre Przywara
2020-01-27  1:14 ` [PATCH v3 3/3] rpi4: Enable GENET Ethernet controller Andre Przywara
2020-01-27 10:09 ` [PATCH v3 0/3] Ethernet support for Raspberry Pi 4 LABBE Corentin
2020-01-27 10:57   ` Amit Tomer
2020-01-27 11:50     ` LABBE Corentin
2020-01-27 12:06       ` Andre Przywara
2020-01-27 13:15         ` LABBE Corentin
2020-01-28 22:21         ` Jaehoon Chung
2020-01-29  8:04           ` Matthias Brugger
2020-02-03  9:48           ` LABBE Corentin
2020-02-17 11:37             ` Jaehoon Chung
2020-02-18  2:13               ` Jaehoon Chung
2020-02-18  9:59                 ` LABBE Corentin
2020-02-03  9:50         ` LABBE Corentin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200203095007.GB4164@Red \
    --to=clabbe@baylibre.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox