From: Marek Vasut <marek.vasut@mailbox.org>
To: Nimesh Acharya <nimeshacharya197@gmail.com>
Cc: u-boot@lists.u-boot-project.org, hsnaves@gmail.com,
marek.vasut+socfpga@mailbox.org, simon.k.r.goldschmidt@gmail.com,
tien.fong.chee@altera.com, trini@konsulko.com
Subject: Re: [PATCH] configs: socfpga_de10_standard: Fix raw partition booting from SDMMC
Date: Tue, 20 Oct 2026 12:28:45 +0200 [thread overview]
Message-ID: <4030a7f1-c924-4d51-bf93-eaaaf8df2ed0@mailbox.org> (raw)
In-Reply-To: <CAMb=oEaXycpsLz6wfxKVqucox+ZuJumMgaz3Q=+dfD8R3o804g@mail.gmail.com>
On 10/20/26 10:35 AM, Nimesh Acharya wrote:
> Thanks for bringing that up. In fact, on running grep -E
> 'SPL_FS_LOAD_PAYLOAD_NAME|MMCSD_FS_BOOT_PARTITION|MMCSD_RAW_MODE|SPL_FS_FAT|SPL_FS_EXT4|SPL_LOAD_FIT|SPL_RAW_IMAGE'
> $B/*/.config
>
> I get this output for the default config:
>
> CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE=0xa2
> # CONFIG_SPL_FS_FAT is not set
> # CONFIG_SPL_LOAD_FIT is not set
> CONFIG_SPL_RAW_IMAGE_SUPPORT=y
> CONFIG_SPL_SYS_MMCSD_RAW_MODE=y
> CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
> # CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION is not set
> # CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE is not set
> CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x200
> CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_DATA_PART_OFFSET=0x0
> # CONFIG_SPL_FS_EXT4 is not set
> CONFIG_SYS_MMCSD_FS_BOOT_PARTITION=1
>
> So, me adding CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION_TYPE=0xa2 again is
> indeed redundant. I'll fix this soon.
Please stop top-posting.
Is CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE=y the only option
you have to add ?
In any case, please do a V2 and make sure the
CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION_TYPE is in the right
place in the defconfig, not at the end.
next prev parent reply other threads:[~2026-10-20 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 20:59 [PATCH] configs: socfpga_de10_standard: Fix raw partition booting from SDMMC Nimesh Acharya
2026-10-19 21:54 ` Marek Vasut
2026-10-20 8:35 ` Nimesh Acharya
2026-10-20 10:28 ` Marek Vasut [this message]
[not found] ` <CAMb=oEYbdBJbQ-sjZ5q5YDXSjgH3j5PdM11smGXxqgGw-e7QQw@mail.gmail.com>
2026-10-20 11:50 ` Nimesh Acharya
2026-10-20 12:45 ` Marek Vasut
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=4030a7f1-c924-4d51-bf93-eaaaf8df2ed0@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=hsnaves@gmail.com \
--cc=marek.vasut+socfpga@mailbox.org \
--cc=nimeshacharya197@gmail.com \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=tien.fong.chee@altera.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
/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.