All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Marek Vasut <marex@denx.de>, Tom Rini <trini@konsulko.com>,
	Simon Glass <sjg@chromium.org>,
	Fabio Estevam <festevam@gmail.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v2] cmd: mmc: allow use of hardware partition names for mmc partconf
Date: Sat, 27 Apr 2024 09:25:44 +0200	[thread overview]
Message-ID: <7aac74dc3adf48f746520fa9e6c83699@manjaro.org> (raw)
In-Reply-To: <CAJ+vNU3U4P0wLcJ=_Bev++bsRF+=2inGEcs3pMuRb4f7ObSjBQ@mail.gmail.com>

Hello Tim and Marek,

On 2024-04-26 19:36, Tim Harvey wrote:
> On Fri, Apr 26, 2024 at 10:25 AM Marek Vasut <marex@denx.de> wrote:
>> On 4/26/24 7:12 PM, Tim Harvey wrote:
>> > +static const char *mmc_partnames[] = {
>> > +     "user",
>> > +     "boot0",
>> > +     "boot1",
>> > +     "gp1",
>> > +     "gp2",
>> > +     "gp3",
>> > +     "gp4",
>> 
>> Uh, maybe gp%d are indexed from zero too ?
>> 
>> (sorry for the confusion)
> 
> but 'mmc hwpartition' does not list them 0 based:
> u-boot=> mmc hwpartition
> switch to partitions #0, OK
> mmc2(part 0) is current device
> Partition configuration:
>         No enhanced user data area
>         No GP1 partition
>         No GP2 partition
>         No GP3 partition
>         No GP4 partition
> 
> I'm ok with either, I'm just not sure what is more understandable and 
> standard.

I can confirm that JEDEC also starts the numbering of the GP
partitions from one in some of its documents.

Though, it's a bit intriguing why the numbering of the boot
partitions starts from zero.  Perhaps there's some good reason
for that difference.

  parent reply	other threads:[~2024-04-27  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 17:12 [PATCH v2] cmd: mmc: allow use of hardware partition names for mmc partconf Tim Harvey
2024-04-26 17:25 ` Marek Vasut
2024-04-26 17:36   ` Tim Harvey
2024-04-26 17:42     ` Marek Vasut
2024-04-27  7:25     ` Dragan Simic [this message]
2024-04-27  7:30       ` Dragan Simic

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=7aac74dc3adf48f746520fa9e6c83699@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=festevam@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=marex@denx.de \
    --cc=sjg@chromium.org \
    --cc=tharvey@gateworks.com \
    --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.