On 2024-04-27 09:25, Dragan Simic wrote:
On 2024-04-26 19:36, Tim Harvey wrote:
On Fri, Apr 26, 2024 at 10:25 AM Marek Vasut <ma...@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.
Hmm, it seems that JEDEC actually starts the numbering of the boot
partitions from one in some of its documents, instead of starting
from zero. I'll try to research that better.
