From: Marco Felsch <m.felsch@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Robert Schwebel <rsc@pengutronix.de>,
Michael Olbrich <m.olbrich@pengutronix.de>,
"distrokit@pengutronix.de" <distrokit@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [DistroKit] [ptxdist] Prepare Image for Raspberry Pi 4
Date: Mon, 14 Nov 2022 11:58:03 +0100 [thread overview]
Message-ID: <20221114105803.6gmyv3fcwz4skzfw@pengutronix.de> (raw)
In-Reply-To: <SN4PR0801MB8017A9D758C4B6BB3D006FAD82059@SN4PR0801MB8017.namprd08.prod.outlook.com>
Hi Pranay,
On 22-11-14, Joshi, Pranay wrote:
> Any help on below query?
I'm not aware of the DistroKit integration nor the Barebox integration,
but maybe I can support you since Ahmad is on vacation. Please see my
question below.
> From: Joshi, Pranay <Pranay.Joshi@bakerhughes.com>
> Sent: Monday, November 7, 2022 5:09 PM
> To: Ahmad Fatoum <a.fatoum@pengutronix.de>; ptxdist@pengutronix.de; Michael Olbrich <m.olbrich@pengutronix.de>
> Cc: Robert Schwebel <rsc@pengutronix.de>; distrokit@pengutronix.de
> Subject: Re: [ptxdist] Prepare Image for Raspberry Pi 4
>
> Hi Ahmad,
>
> Thanks for your response.
>
> We prepared images for the platform-rpi and platform-v7a using
> Distrokit "next" branch, as you mentioned it's having support of RPi
> for 32-bit. When prepared image is loaded into SD card and powered
> Raspberry Pi 4B, we are getting error "start_cd.elf: is not
> compatible".
Can you please provide the whole error string barebox is printing?
> Is there any configuration needs to update? Or anything else needs to
> do?
If you can provide us the whole barebox log we can see a bit more what
is going on.
Regards,
Marco
next prev parent reply other threads:[~2022-11-14 10:58 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
[not found] ` <PH0PR08MB80142B5E46E08F7A38197224823C9@PH0PR08MB8014.namprd08.prod.outlook.com>
[not found] ` <SN4PR0801MB8017A9D758C4B6BB3D006FAD82059@SN4PR0801MB8017.namprd08.prod.outlook.com>
2022-11-14 10:58 ` Marco Felsch [this message]
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=20221114105803.6gmyv3fcwz4skzfw@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--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