public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Simon Glass <sjg@chromium.org>
Cc: Stefano Babic <sbabic@denx.de>,
	Fabio Estevam <festevam@gmail.com>,
	"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
	u-boot@lists.denx.de, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 00/12] imx9: switch to bootstd for i.MX93/1 EVK/QSB and i.MX8M EVK
Date: Mon, 6 Jan 2025 09:33:11 +0800	[thread overview]
Message-ID: <20250106013311.GA8414@localhost.localdomain> (raw)
In-Reply-To: <CAFLszTi_px3qRGvpcC5WKLw+r5BqqQciOP-Vg1LEN+rt9876wQ@mail.gmail.com>

Hi Simon,

On Sun, Jan 05, 2025 at 08:30:55AM +1300, Simon Glass wrote:
>Hi Peng,
>
>On Sat, 4 Jan 2025 at 16:19, Peng Fan (OSS) <peng.fan@oss.nxp.com> wrote:
>>
>> Switch to bootstd for NXP i.MX9/8M boards with a bsp_bootcmd as fallback.
>>
[...]
>>
>
>This also switches to a text environment, great!
>
>For bsp_bootcmd is it possible to create a bootmeth for your use case?
>If you would like to take a look (separate from this series), I could
>help with any issues that come up.

I just give a quick look of bootmeth, seems needs extlinux or bootscript
(boot.scr). But both are used on NXP i.MX release as of now. In NXP
releases, we put all script in the U-Boot ENV.

Do you have suggestions how to move to support bootmeth.

Thanks,
Peng.

>
>Regards,
>Simon

  reply	other threads:[~2025-01-06  0:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-04  4:25 [PATCH 00/12] imx9: switch to bootstd for i.MX93/1 EVK/QSB and i.MX8M EVK Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 01/12] imx: imx93_evk: switch to BOOTSTD Peng Fan (OSS)
2025-01-06 11:06   ` Fabio Estevam
2025-01-04  4:25 ` [PATCH 02/12] imx: imx93_qsb: " Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 03/12] imx: imx91_evk: " Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 04/12] imx: imx8mp_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 05/12] imx: imx8mp_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 06/12] imx: imx8mn_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-06 11:09   ` Fabio Estevam
2025-01-04  4:25 ` [PATCH 07/12] imx: imx8mn_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 08/12] imx: imx8mm_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 09/12] imx: imx8mm_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 10/12] imx: imx8mq_evk: Enable dynamic settings to mmcdev and mmcroot Peng Fan (OSS)
2025-01-06 11:11   ` Fabio Estevam
2025-01-04  4:25 ` [PATCH 11/12] imx: imx8mq_evk: Switch to BOOTSTD Peng Fan (OSS)
2025-01-04  4:25 ` [PATCH 12/12] imx: imx93-11x11-evk: drop duplicated nodes Peng Fan (OSS)
2025-01-04 19:30 ` [PATCH 00/12] imx9: switch to bootstd for i.MX93/1 EVK/QSB and i.MX8M EVK Simon Glass
2025-01-06  1:33   ` Peng Fan [this message]
2025-01-06  1:02     ` Simon Glass
2025-01-06  1:14       ` Peng Fan
2025-01-06 12:15         ` Simon Glass
2025-01-06 23:45           ` Tony Dinh
2025-01-13  9:48             ` Frieder Schrempf
2025-01-14 13:13               ` Simon Glass
2025-01-07  1:39           ` Peng Fan
2025-01-08 16:27             ` Simon Glass

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=20250106013311.GA8414@localhost.localdomain \
    --to=peng.fan@oss.nxp.com \
    --cc=festevam@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=sbabic@denx.de \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.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