From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: ptxdist@pengutronix.de, "Joshi,
Pranay" <Pranay.Joshi@bakerhughes.com>,
Michael Olbrich <m.olbrich@pengutronix.de>
Cc: Robert Schwebel <rsc@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4
Date: Mon, 31 Oct 2022 09:01:26 +0100 [thread overview]
Message-ID: <50eb7f21-9075-abf8-27f4-6064bb3f1194@pengutronix.de> (raw)
In-Reply-To: <PH0PR08MB801478F4321D6EC7F26475AB82329@PH0PR08MB8014.namprd08.prod.outlook.com>
Hello Pranay,
On 28.10.22 14:47, Joshi, Pranay wrote:
> Hi Michael,
>
> Thank you for your support.
>
> Earlier we were stuck in building toolchain and root filesystem for Raspberry Pi platform using PTXDist Tool, OSELAS Toolchain and DistroKit. We have been successfully able to prepare an image with the solutions provided by you.
Cc += DistroKit Mailing List <distrokit@pengutronix.de>
The PTXdist mailing list is rather for the build system itself, toolchain
and upstream rules and not about particular board support packages.
> We tried prepared image over RPi 4, once we have powered up RPi 4 it is showing an error like "This board requires newer software".
>
> After some inspection we understood that the prepared image can support RPi 3.
The DistroKit "next" branch supports Raspberry Pi 4 in 32-bit mode. The changes are not yet
in "master". The resulting image can be installed on Rasperry Pi 2, 3, CM3 and 4. Keep in mind
that I did not test rpi4 support on a CM4. It may need some slight tweaking.
> Now can you please give some path to prepare supported image for RPi 4 using PTXDist tool?
>
> From where can we get an idea to modify an image for a new platform like RPi 4 using PTXDist?
If you are willing to help, adding support for Raspberry Pi 3 and 4 64-bit to DistroKit
platform-v8a should be quite straight-forward. All components built by platform-v7a for
Raspberry Pi can be configured for 64-bit (bootloader, kernel, rootfs, rpi firmware),
but some integration into DistroKit is still required:
- Add a new barebox-rpi.{make,in} rule to platform-v8a, which collects the same files
as barebox-rpi2.make in platform-v7a. platform-v7a has barebox-common, but we don't
have that for platform-v8a, so either add it or add it as a standalone rule
- copy the barebox-rpi3.config to platform-v8a and change it to have CONFIG_64BIT=y
- configure the kernel to enable all the Raspberry Pi 4 related drivers
- Have DistroKit build the Raspberry Pi 4 device trees and generate bootspec entries using
them
- ensure config.txt has arm_64bit=1
- Add image recipes that pull in the firmware, bootloader and rootfs
When done correctly, you will end up with a rpi.hdimg that can be booted from SD
on either Rpi3 or Rpi4.
Cheers,
Ahmad
>
>
> Pranay Joshi
>
> Lead Engineer-Firmware Engineering
>
> Drilling Services
>
> Baker Hughes
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next parent reply other threads:[~2022-10-31 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR08MB801478F4321D6EC7F26475AB82329@PH0PR08MB8014.namprd08.prod.outlook.com>
2022-10-31 8:01 ` Ahmad Fatoum [this message]
[not found] ` <PH0PR08MB80142B5E46E08F7A38197224823C9@PH0PR08MB8014.namprd08.prod.outlook.com>
[not found] ` <SN4PR0801MB8017A9D758C4B6BB3D006FAD82059@SN4PR0801MB8017.namprd08.prod.outlook.com>
2022-11-14 10:58 ` Marco Felsch
2022-11-15 6:05 ` Joshi, Pranay
2022-11-15 9:41 ` Marco Felsch
2022-11-15 9:47 ` Joshi, Pranay
2022-11-15 10:04 ` Marco Felsch
2022-11-15 10:16 ` Roland Hieber
2022-11-15 10:30 ` Joshi, Pranay
2022-11-15 11:00 ` Marco Felsch
2022-11-15 11:27 ` Joshi, Pranay
2022-12-01 12:09 ` Ahmad Fatoum
2022-12-02 5:39 ` Joshi, Pranay
2022-12-02 6:14 ` Ahmad Fatoum
2022-12-05 6:00 ` Joshi, Pranay
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=50eb7f21-9075-abf8-27f4-6064bb3f1194@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=Pranay.Joshi@bakerhughes.com \
--cc=distrokit@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rsc@pengutronix.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