From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: devel@edk2.groups.io, osde@linux.microsoft.com
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel][PATCH v1 1/1] ArmVirtPkg: ArmVirtQemu: Add Graphics and Input
Date: Sat, 19 Aug 2023 21:39:43 +0200 [thread overview]
Message-ID: <65f0e7ea-3f64-9f5c-4a90-8daec711898f@linaro.org> (raw)
In-Reply-To: <20230818181751.12308-1-osde@linux.microsoft.com>
W dniu 18.08.2023 o 20:17, Oliver Smith-Denny pisze:
> Currently, unlike OVMF, ArmVirtQemu does not display any graphics, only
> the QEMU monitor. Graphics are helpful to confirm booting into an OS is
> successful, interacting with the EFI shell while getting separate
> logging messages, etc.
Ah, that "but on x86 it is different" again ;D
I asked QEMU (and libvirt) devs in past why AArch64/virt lacks USB while
both x86/pc and x86/q35 have it. The answer was something like "it was a
mistake we do not plan to repeat". And hint that whatever uses either
QEMU or libvirt should take care of adding hardware they expect.
Took me a while to convince OpenStack Nova people that it is not
QEMU/libvirt fault ;D
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107894): https://edk2.groups.io/g/devel/message/107894
Mute This Topic: https://groups.io/mt/100826022/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-08-19 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 18:17 [edk2-devel][PATCH v1 1/1] ArmVirtPkg: ArmVirtQemu: Add Graphics and Input Oliver Smith-Denny
2023-08-18 21:05 ` Ard Biesheuvel
2023-09-05 16:05 ` Oliver Smith-Denny
2023-09-06 9:15 ` Ard Biesheuvel
2023-08-19 19:39 ` Marcin Juszkiewicz [this message]
2023-08-19 22:10 ` Pedro Falcato
2023-08-21 14:38 ` Gerd Hoffmann
2023-08-21 14:51 ` Leif Lindholm
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=65f0e7ea-3f64-9f5c-4a90-8daec711898f@linaro.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