From: Xiangyu Chen <xiangyu.chen@windriver.com>
To: Paul Barker <paul@pbarker.dev>,
xiangyu.chen@eng.windriver.com,
openembedded-core@lists.openembedded.org, arindam.nath@amd.com
Subject: Re: [OE-core][PATCH] grub: update search parameter
Date: Tue, 31 Mar 2026 10:57:48 +0800 [thread overview]
Message-ID: <20fd5dc4-ef85-49d6-931b-7a8ea3f94c04@windriver.com> (raw)
In-Reply-To: <2c704d3b5aa8852a3d4e24143fdedb8f530517ae.camel@pbarker.dev>
Hi Paul,
On 3/5/26 19:49, Paul Barker wrote:
> I'm not sure that this can work for all use cases. The grub
> documentatation for hints says "First try the device HINT" (i.e. it's
> explicitly a device), whereas the documentation for cmdpath says that it
> is "an absolute directory name".
While the documentation defines $cmdpath as a directory and hints as
devices, grub’s internal implementation of
grub_disk_open (grub-core/kern/disk.c [1]) is designed to handle this
exact "device+path" format.
When a hint like (hd0,gpt1)/EFI/BOOT/ is passed, grub_disk_open calls
find_part_sep to locate the partition/path delimiter.
It then uses grub_memcpy to extract only the device part (e.g., (hd0)
into the raw buffer for the disk driver.
The remaining string (gpt1)/EFI/BOOT/) is passed to
grub_partition_probe, which identifies the partition and gracefully
ignores the trailing directory path.
The current syntax ($cmdpath) results in double parentheses ((hd0...))
if the variable is already populated.
In grub_disk_open, this extracts a malformed device name ((hd0 which no
driver can open, triggering a hard no such device error.
Ref:
[1]
https://elixir.bootlin.com/grub/grub-2.14/source/grub-core/kern/disk.c#L192
Br,
Xiangyu
next prev parent reply other threads:[~2026-03-31 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:19 [OE-core][PATCH] grub: update search parameter Xiangyu Chen
2026-03-05 11:49 ` Paul Barker
2026-03-31 2:57 ` Xiangyu Chen [this message]
2026-04-23 6:04 ` Xiangyu Chen
2026-04-23 6:38 ` Yoann Congal
2026-04-23 7:18 ` Xiangyu Chen
2026-04-23 7:29 ` Yoann Congal
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=20fd5dc4-ef85-49d6-931b-7a8ea3f94c04@windriver.com \
--to=xiangyu.chen@windriver.com \
--cc=arindam.nath@amd.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
--cc=xiangyu.chen@eng.windriver.com \
/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