From: Elliott Mitchell <ehem+xen@m5p.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>
Cc: xen-devel@lists.xenproject.org
Subject: ACPI/UEFI support for Xen/ARM status?
Date: Thu, 11 Nov 2021 20:27:52 -0800 [thread overview]
Message-ID: <YY3tSAFTCR4r2FaI@mattapan.m5p.com> (raw)
I've been busy with another part of this project, so I've lost track of
progress on ACPI/UEFI support on ARM.
Last I'd read full support for ACPI/UEFI seemed a ways off. Using a stub
domain to constrain ACPI table parsing seemed the favored approach. I
was under the impression that would take some time.
What is the status? Do the Xen/ARM leads have any guesses for when full
ACPI/UEFI support might reach completion?
I noticed Linux made full ACPI/UEFI support mandatory for ARM64 before
3.19, so Xen's seems far behind the curve here.
While incidents of garbled ACPI tables are notorious, those are notable
due to being rare. Whereas I've had terrible luck with device-trees.
The instances of any given OS *not* breaking device-trees with even
patch-level changes are rare.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
next reply other threads:[~2021-11-12 4:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 4:27 Elliott Mitchell [this message]
2021-11-12 5:54 ` ACPI/UEFI support for Xen/ARM status? Henry Wang
2021-11-12 15:44 ` Elliott Mitchell
2021-11-12 16:02 ` Julien Grall
2021-11-12 16:52 ` Elliott Mitchell
2021-11-12 17:38 ` Julien Grall
2021-11-12 21:15 ` Elliott Mitchell
2021-11-12 22:08 ` Julien Grall
2021-11-12 22:32 ` Elliott Mitchell
2021-11-12 23:00 ` Julien Grall
2021-11-13 1:03 ` Elliott Mitchell
2021-11-15 10:06 ` Bertrand Marquis
2021-11-15 21:30 ` Elliott Mitchell
2021-11-15 10:13 ` Jan Beulich
2021-11-15 19:09 ` Julien Grall
2021-11-16 7:18 ` Jan Beulich
2021-11-23 2:22 ` Elliott Mitchell
2021-11-29 16:28 ` Elliott Mitchell
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=YY3tSAFTCR4r2FaI@mattapan.m5p.com \
--to=ehem+xen@m5p.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.