All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Heiko Schocher <hs@nabladev.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Adrian Freihofer <adrian.freihofer@siemens.com>,
	Dmitrii Merkurev <dimorinny@google.com>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v1 1/2] fastboot: mmc: make boot partition offset configurable
Date: Mon, 26 Jan 2026 09:41:59 +0800	[thread overview]
Message-ID: <aXbGZ22OTwTbbGEw@shlinux89> (raw)
In-Reply-To: <20260124054712.7939-2-hs@nabladev.com>

Hi Heiko,

On Sat, Jan 24, 2026 at 06:47:10AM +0100, Heiko Schocher wrote:
>From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
>Add a weak function fb_mmc_get_boot_offset() to allow to override
>the default offset (0) when writing to eMMC boot partitions.

>This enables support for devices with non-standard boot partition
>layouts, such as those requiring an offset for correct bootloader
>placement.
>
>The imx8qxp processors are an example where older revisions need a
>32kB offset.
>
>Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
>Signed-off-by: Heiko Schocher <hs@nabladev.com>

I am thinking to write as below:

i.MX8QXP rev C.0 requires boot container stored at offset 0KB for eMMC,
while i.MX8QXP pre C.0 requires boot container stored at offset 32KB for eMMC.

To use one U-Boot binary to support different chip revisions, introduce
fb_mmc_get_boot_offset() to allow override the default offset when writting
to eMMC boot partitions.

This enables support for devices with non-standard boot partition
layouts, such as those requiring an offset for correct bootloader
placement.

Regards
Peng

  reply	other threads:[~2026-01-26  1:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24  5:47 [PATCH v1 0/2] fastboot: mmc: fix bootloader offset Heiko Schocher
2026-01-24  5:47 ` [PATCH v1 1/2] fastboot: mmc: make boot partition offset configurable Heiko Schocher
2026-01-26  1:41   ` Peng Fan [this message]
2026-02-06 10:20   ` Mattijs Korpershoek
2026-01-24  5:47 ` [PATCH v1 2/2] arch: imx8qxp: Override weak fb_mmc_get_boot_offset function Heiko Schocher
2026-01-26  1:44   ` Peng Fan
2026-02-06 10:24   ` Mattijs Korpershoek
2026-01-26  9:48 ` [PATCH v1 0/2] fastboot: mmc: fix bootloader offset Mattijs Korpershoek
2026-01-26 15:46   ` Heiko Schocher
2026-01-29 10:09     ` Mattijs Korpershoek
2026-01-29 10:41       ` Heiko Schocher
2026-01-29 14:09         ` Mattijs Korpershoek
2026-01-30 16:35           ` Mattijs Korpershoek
2026-02-02  5:12             ` Heiko Schocher
2026-02-02  9:34               ` Mattijs Korpershoek

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=aXbGZ22OTwTbbGEw@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=dimorinny@google.com \
    --cc=hs@nabladev.com \
    --cc=mkorpershoek@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.