From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Vincent Davis Jr" <vince@underview.tech>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v5 1/3] bootimg_pcbios: initial import of grub legacy bios boot
Date: Fri, 01 Aug 2025 11:56:24 +0200 [thread overview]
Message-ID: <DBR027884PSE.3LDB5GXMMT6YN@bootlin.com> (raw)
In-Reply-To: <20250801021607.511597-2-vince@underview.tech>
On Fri Aug 1, 2025 at 4:16 AM CEST, Vincent Davis Jr 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>
> ---
Hi Vincent,
It looks like this is breaking some tests:
ERROR: core-image-minimal-dev-1.0-r0 do_image_wic: Execution of '/srv/pokybuild/yocto-worker/qemux86/build/build/tmp/work/qemux86-poky-linux/core-image-minimal-dev/1.0/temp/run.do_image_wic.2578330' failed with exit code 1
...
| output: Error: Can't have the end before the start! (start sector=2048 length=0)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/2118
https://autobuilder.yoctoproject.org/valkyrie/#/builders/78/builds/2172
Can you have a look at these failures please?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-08-01 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 2:16 [PATCH v5 1/3] bootimg_pcbios: initial import of grub legacy bios boot Vincent Davis Jr
2025-08-01 2:16 ` [PATCH v5 2/3] bootimg_pcbios: final import of grub legacy boot Vincent Davis Jr
2025-08-01 2:16 ` [PATCH v5 3/3] oe-selftest: add wic.Wic.test_grub_install_pcbios Vincent Davis Jr
2025-08-01 9:56 ` Mathieu Dubois-Briand [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=DBR027884PSE.3LDB5GXMMT6YN@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--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