public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Philip Oberfichtner <pro@denx.de>
Cc: u-boot@lists.denx.de, Peng Fan <peng.fan@nxp.com>,
	Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: Changing eMMC boot partition size
Date: Tue, 8 Nov 2022 13:30:25 -0500	[thread overview]
Message-ID: <20221108183025.GU6335@bill-the-cat> (raw)
In-Reply-To: <c5f59cc65ff6b6447f8c51a00e315df3aca6d25c.camel@denx.de>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

On Tue, Nov 08, 2022 at 06:34:18PM +0100, Philip Oberfichtner wrote:
> Hi everybody,
> 
> I have a question regarding changing the eMMC boot partition size.
> According the the JEDEC eMMC spec it is read-only (BOOT_SIZE_MULT
> register).
> 
> But we still have mmc_boot_partition_size_change() in
> drivers/mmc/mmc_boot.c. It contains the comment
> 
> /* Only use this command for raw EMMC moviNAND. Enter backdoor mode */
> 
> What is moviNAND? My research pointed me to Samsung products only. So
> is changing the boot partition size vendor specific or can it be used
> more generally?
> 
> To be specific, I use the Kioxia THGBMJG6C1LBAB7 eMMC chip.

Yes, moviNAND was some Samsung technology that may or may not still be
used on some platforms. And yes, some eMMC parts do allow for boot
partitions to be resized but such information is often under NDA, so
contacting the hardware vendor or looking for eMMC chip documentation
may be helpful here.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-11-08 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 17:34 Changing eMMC boot partition size Philip Oberfichtner
2022-11-08 18:30 ` Tom Rini [this message]
2022-11-14  9:06   ` Jaehoon Chung

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=20221108183025.GU6335@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=jh80.chung@samsung.com \
    --cc=peng.fan@nxp.com \
    --cc=pro@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox