From: "Andrey Popov" <andrey.popov@yadro.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] image-live: Add support for building EFI-bootable ISO images for non-x86-based archs
Date: Tue, 28 Nov 2023 11:07:45 -0800 [thread overview]
Message-ID: <5820.1701198465891150571@lists.openembedded.org> (raw)
In-Reply-To: <53356C03-3699-43FC-B8A5-70609982F612@arm.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Hello, Ross!
Currently, we are using a Yocto-based network equipment software distribution called TanoWRT (https://tano-systems.gitlab.io/meta-tanowrt/).
This distribution provides a way to create images that can be used to facilitate network boot process using PXE. Those images are actually ISO images, and they work well for x86-based platforms, since they use already available syslinux stubs that were used for that purpose for a very long time. Unfortunately, syslinux does not support platforms that use CPU of different architectures, which, however, still support network boot process as per the UEFI spec. For those platforms, the image that is used for network boot is still the very same ISO image, the only difference is that it has the 2nd stage bootloader in a standard EFI PE format prepended to it.
I hope that my explanation answers you question.
Best regards, Andrey.
[-- Attachment #2: Type: text/html, Size: 920 bytes --]
next prev parent reply other threads:[~2023-11-28 19:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 15:12 [PATCH v2] image-live: Add support for building EFI-bootable ISO images for non-x86-based archs Andrey Popov
2023-11-28 17:55 ` [OE-core] " Ross Burton
2023-11-28 19:00 ` Chuck Wolber
2023-11-28 19:50 ` Ross Burton
2023-11-29 7:17 ` Chuck Wolber
2023-11-28 19:07 ` Andrey Popov [this message]
2023-11-29 11:50 ` Ross Burton
2023-11-29 17:26 ` Andrey Popov
2023-11-30 15:27 ` [OE-core] " Steve Sakoman
2023-11-30 16:01 ` Ross Burton
2023-11-30 16:20 ` Andrey Popov
2023-12-01 22:58 ` [OE-core] " Steve Sakoman
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=5820.1701198465891150571@lists.openembedded.org \
--to=andrey.popov@yadro.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox