From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Corvin Köhne" <C.Koehne@beckhoff.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Rebecca Cran <rebecca@bsdio.com>,
Peter Grehan <grehan@freebsd.org>,
FreeBSD Virtualization <freebsd-virtualization@freebsd.org>
Subject: Re: [edk2-devel] [PATCH 0/1] OvmfPkg/Bhyve: QemuFwCfg support
Date: Tue, 29 Mar 2022 15:35:52 +0200 [thread overview]
Message-ID: <20220329133552.t2ypz3nunywxjkia@sirius.home.kraxel.org> (raw)
In-Reply-To: <02bd2bef03484e189f04dc39a6f3ad66@beckhoff.com>
Hi,
> Personally, I would like to use plain OVMF without any bhyve specific patches
> as firmware for bhyve. So, I want to go the qemu route but there's some more
> work to do. I already took a look at how qemu creates ACPI tables but don't
> understand it yet. Would be very grateful if you or someone else could help
> me with that. If someone knows where to find more information about it,
> it would also be helpful.
I think the best documentation you can find is
hw/acpi/bios-linker-loader.c in the qemu source tree.
It's a mini-language telling the firmware about the allocations needed,
about pointers (xsdt references for example) so tables are relocatable,
about checksum needing updates etc.
I think qemu generates everything meanwhile, but it should be possible
to get started with iasl-compiled blobs for tables which don't change,
i.e. start with a static dsdt so you don't need a aml generator for the
first revision.
take care,
Gerd
prev parent reply other threads:[~2022-03-29 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 6:54 [PATCH 0/1] OvmfPkg/Bhyve: QemuFwCfg support Corvin Köhne
2022-03-29 6:54 ` [PATCH 1/1] OvmfPkg/BhyveBhfPkg: add support for QemuFwCfg Corvin Köhne
2022-03-29 9:24 ` [edk2-devel] " Gerd Hoffmann
2022-03-29 9:59 ` Corvin Köhne
2022-03-29 9:14 ` [edk2-devel] [PATCH 0/1] OvmfPkg/Bhyve: QemuFwCfg support Gerd Hoffmann
2022-03-29 9:57 ` Corvin Köhne
2022-03-29 11:30 ` Gerd Hoffmann
2022-03-29 11:53 ` Corvin Köhne
2022-03-29 13:35 ` Gerd Hoffmann [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-list 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=20220329133552.t2ypz3nunywxjkia@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/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