mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Stefano Manni <stefano.manni@gmail.com>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: [RFC] board imx8qxp-mek
Date: Thu, 15 Jan 2026 11:46:35 +0100	[thread overview]
Message-ID: <beb2d064-bd5a-4d97-91be-55af7d81ecd2@pengutronix.de> (raw)
In-Reply-To: <OR4V8T.50BC0FSNYML@gmail.com>

Hi Stefano,

On 1/14/26 5:35 PM, Stefano Manni wrote:
> Hi,
> 
> I'd like to add the board imx8qxp-mek from NXP.
> Since the SoC is already supported by barebox, it should be quite
> straightforward
> to add the new board but I need to understand if the starting point is
> u-boot [1]
> or something else.
> 
> Any comment and recommendation is appreciated.

I think you may have been misled by NXP's naming scheme.
barebox indeed has good support for the i.MX8*M*, including
i.MX8MQ, i.MX8MM, i.MX8MN and i.MX8MP.

i.MX8Q (no M!) is a different SoC: It has different CPUs and importantly
for barebox, very different startup than the i.MX8M as its internal
Cortex-M4 (the SCU) is what first boots up in this SoC and one would
first need to teach barebox how to communicate with this process as well
as implement the new boot image format that is required.

AFAIU, the Linux upstream situation for these other i.MX8's is also
worse than for the i.MX8M.

Cheers,
Ahmad

> [1] https://elixir.bootlin.com/u-boot/v2026.01/source/board/freescale/
> imx8qxp_mek
> 
> Thank you.
> Best,
> Stefano
> 
> 
> 
> 

-- 
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 |




      reply	other threads:[~2026-01-15 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14 16:35 Stefano Manni
2026-01-15 10:46 ` Ahmad Fatoum [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=beb2d064-bd5a-4d97-91be-55af7d81ecd2@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=stefano.manni@gmail.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