From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Athaariq Ardhiansyah <foss@athaariq.my.id>
Cc: Martin Bark <martin@barkynet.com>,
Julien Grossholtz <julien.grossholtz@openest.io>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 3/3] board/raspberrypi: add support for Raspberry Pi 5
Date: Sun, 14 Jul 2024 18:59:11 +0200 [thread overview]
Message-ID: <20240714185911.2740dc9d@windsurf> (raw)
In-Reply-To: <20240714160457.39434-3-foss@athaariq.my.id>
Hello,
On Sun, 14 Jul 2024 23:04:54 +0700
Athaariq Ardhiansyah <foss@athaariq.my.id> wrote:
> Since the last Raspberry Pi 5 submission has no progress, I'm submitting
> these patches anyway. The newly released Raspberry Pi 5 board shares
> similar software structure except it has less proprietary API.
> Therefore, rpi-userland and all of raspberry-centric GPIO utilities are
> no longer supported.
>
> Keep in mind that RPi 5 has no native 32-bit support due to Cortex-A76
> processor specification. That is the reason why I did not add _64.
>
> Signed-off-by: Athaariq Ardhiansyah <foss@athaariq.my.id>
>
> ---
> Changes v1 -> v2:
> - Fix missing newlines due to terminal issue
>
> Changes v3 -> v4:
> - Rebase to master
> - Drop 4K page size, until we figured out how to run 32bit userspace
> on top of 64bit kernel
> - Change back from commit ID to commit tag
> - Rewrite the commit description
> - Fix incorrect CPU from upstream config, RPi5 has no LITTLE.big
>
> Signed-off-by: Athaariq Ardhiansyah <foss@athaariq.my.id>
> ---
> board/raspberrypi/config_5.txt | 42 +++++++++++++++++++
> .../patches/linux-headers/linux-headers.hash | 1 -
> board/raspberrypi/patches/linux/linux.hash | 2 +-
> configs/raspberrypi5_defconfig | 17 ++++----
> 4 files changed, 50 insertions(+), 12 deletions(-)
> delete mode 120000 board/raspberrypi/patches/linux-headers/linux-headers.hash
Thanks, but here you're submitted a diff against the previous
raspberrypi5_defconfig submission. Please submit a full patch adding
the complete support for RPi5, not a diff against some random other
patch posted on the mailing list.
Thanks!
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:[~2024-07-14 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 16:04 [Buildroot] [PATCH v4 1/3] package/rpi-firmware: bump version to 1.20240529 Athaariq Ardhiansyah
2024-07-14 16:04 ` [Buildroot] [PATCH v4 2/3] package/raspberrypi-usbboot: bump version to master (commit 4a3d311) Athaariq Ardhiansyah
2024-07-14 16:57 ` Thomas Petazzoni via buildroot
2024-07-14 16:04 ` [Buildroot] [PATCH v4 3/3] board/raspberrypi: add support for Raspberry Pi 5 Athaariq Ardhiansyah
2024-07-14 16:59 ` Thomas Petazzoni via buildroot [this message]
2024-07-14 16:56 ` [Buildroot] [PATCH v4 1/3] package/rpi-firmware: bump version to 1.20240529 Thomas Petazzoni via buildroot
2024-07-15 9:10 ` Gaël PORTAY
2024-07-15 12:15 ` Thomas Petazzoni via buildroot
2024-07-15 16:11 ` Athaariq Ardhiansyah
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=20240714185911.2740dc9d@windsurf \
--to=buildroot@buildroot.org \
--cc=foss@athaariq.my.id \
--cc=julien.grossholtz@openest.io \
--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