From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: vince@underview.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v6 1/3] bootimg_pcbios: initial import of grub legacy bios boot
Date: Thu, 07 Aug 2025 12:35:49 +0100 [thread overview]
Message-ID: <567c2becce21c752b39d412b8c80770d12415b88.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250802220229.2826203-2-vince@underview.tech>
On Sat, 2025-08-02 at 18:02 -0400, Vincent Davis Jr via lists.openembedded.org wrote:
> Moves syslinux config file creation,
> partition prepare, and mbr install
> tasks into there own seperate functions
> before removal from SourcePlugin class
> functions.
>
> Add 3 new functions for creation of
> grub config, preparing boot partition
> to contain grub config and modules,
> and install grub boot.img to resulting
> wic image.
>
> Signed-off-by: Vincent Davis Jr <vince@underview.tech>
> ---
> .../lib/wic/plugins/source/bootimg_pcbios.py | 351 +++++++++++++++++-
> 1 file changed, 350 insertions(+), 1 deletion(-)
Thanks, this is definitely getting better and more readable. We
discussed this a bit on the patch review call and there are a few more
tweaks which would help this be more understandable. We really need the
commits to show isolated specific changes and also explain both what
they're doing, and why.
I'd suggest the first commit should create the new grub functions and
call them from the existing call sites. This way we can just see the
code move without new code (such as the syslinux code) or any
functionality changes.
The second commit can then add the loader selection code (just calling
into grub).
The third commit would then add the new syslinux functions and their
calls.
The fourth patch adding a test is good.
The commit messages (and summary) should make it clear that the
existing code only supports grub and that the changes add syslinux
support alongside grub. It would also be helpful to mention what
happens to the defaults, I know that has changed as the patch series
has evolved.
Cheers,
Richard
prev parent reply other threads:[~2025-08-07 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-02 22:02 [PATCH v6 1/3] bootimg_pcbios: initial import of grub legacy bios boot Vincent Davis Jr
2025-08-02 22:02 ` [PATCH v6 2/3] bootimg_pcbios: final " Vincent Davis Jr
2025-08-02 22:02 ` [PATCH v6 3/3] oe-selftest: add wic.Wic.test_grub_install_pcbios Vincent Davis Jr
2025-08-07 11:35 ` Richard Purdie [this message]
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=567c2becce21c752b39d412b8c80770d12415b88.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=vince@underview.tech \
/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