From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Gaël PORTAY" <gael.portay@rtone.fr>
Cc: Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
Martin Bark <martin@barkynet.com>,
Julien Grossholtz <julien.grossholtz@openest.io>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [v1 0/4] [PATCH 0/3] Add support for Pi5
Date: Thu, 23 Nov 2023 11:12:33 +0100 [thread overview]
Message-ID: <20231123111233.24b5dbf2@windsurf> (raw)
In-Reply-To: <20231121193448.1151936-1-gael.portay@rtone.fr>
On Tue, 21 Nov 2023 20:34:44 +0100
Gaël PORTAY <gael.portay@rtone.fr> wrote:
> The output boots fine and it runs getty on uart and virtual tty if it is
> built using the toolchain built by buildroot.
>
> The output boots the kernel but the kernel cannot run the init process
> if it is built using the bootlin prebuilt toolchain. Something is broken
> due to the 16k MMU page-size :(
I *think* this is expected. The Bootlin toolchains are built for the
default page size of 4KB, so the libc in those toolchains expects 4KB
pages, and this breaks if you mix it with code that was built for 16 KB
page size.
> Question: the device-tree overlays are taken from the rpi-firmware; is
> there a plan to compile the one from the downstream kernel sources
> instead? by tweaking the linux.mk maybe?
The problem here is that it would be a tweak in linux.mk that is
specific to how the downstream RPi kernel does it. But the mainline
kernel has grown support for building DT overlays too. Is it similar to
how the downstream RPi kernel does it?
Which tweak would be needed in linux.mk to build overlays in the
downstream RPi kernel?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-23 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 19:34 [Buildroot] [v1 0/4] [PATCH 0/3] Add support for Pi5 Gaël PORTAY
2023-11-21 19:34 ` [Buildroot] [v1 1/4] arch: add support 16k page size on ARM64 Gaël PORTAY
2023-11-21 19:34 ` [Buildroot] [v1 2/4] package/rpi-firmware: bump version for pi5 support Gaël PORTAY
2024-01-20 18:16 ` Yann E. MORIN
2023-11-21 19:34 ` [Buildroot] [v1 3/4] configs/raspberrypi*: bump kernel version to feb4ea5 (6.1.55) Gaël PORTAY
2024-02-05 12:03 ` Giulio Benetti
2023-11-21 19:34 ` [Buildroot] [v1 4/4] configs: add raspberrypi 5 defconfig Gaël PORTAY
2024-02-05 14:10 ` Giulio Benetti
2023-11-23 10:12 ` Thomas Petazzoni via buildroot [this message]
2023-11-23 15:25 ` [Buildroot] [v1 0/4] [PATCH 0/3] Add support for Pi5 Gaël PORTAY
2023-11-23 15:38 ` Gaël PORTAY
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=20231123111233.24b5dbf2@windsurf \
--to=buildroot@buildroot.org \
--cc=gael.portay@rtone.fr \
--cc=julien.grossholtz@openest.io \
--cc=mahyar.koshkouei@gmail.com \
--cc=martin@barkynet.com \
--cc=thomas.petazzoni@bootlin.com \
/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