From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@ml01.01.org>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH 00/11] OvmfPkg, ArmVirtPkg: GOP driver for the VirtIo GPU (virtio-gpu-pci)
Date: Fri, 2 Sep 2016 00:02:32 +0200 [thread overview]
Message-ID: <f7abf2a5-4836-42c9-fffc-ad05095a7a09@redhat.com> (raw)
In-Reply-To: <20160819124932.29711-1-lersek@redhat.com>
On 08/19/16 14:49, Laszlo Ersek wrote:
> - Also tested loading and launching Linux from GRUB. Here the results
> differ of course: x86_64 Fedora 24 drives virtio-gpu-pci with its
> native driver without problems, whereas AARCH64 Fedora 23 doesn't even
> look for virtio-gpu-pci, apparently.
Update:
Once booted from GRUB -- on top of OVMF / ArmVirtQemu respectively --,
both x86_64 and aarch64 Fedora *24* guests work well with
virtio-gpu-pci, as far as the character console (tty1, "virtiodrmfb") is
concerned.
However, for getting an X.org graphical environment (such as Xfce) to
work with virtio-gpu-pci, more gymnastics are needed in the guest, on
both guest arches.
This is because X.org considers "virtio-gpu-pci" a secondary graphics
card, and it won't use it even in a single-head setup *unless* the BusID
option is specified in the X.org config file, in the Device section.
Refer to <http://linux.die.net/man/5/xorg.conf>:
BusID bus-id [...] when using a secondary graphics card in a
single-head configuration, this entry is mandatory
After I placed
Section "Screen"
Identifier "Default Screen"
Device "Default Device"
Monitor "Default Monitor"
EndSection
Section "Device"
Identifier "Default Device"
Driver "modesetting"
BusID "PCI:0:1:0"
EndSection
Section "Monitor"
Identifier "Default Monitor"
Option "PreferredMode" "1024x768"
EndSection
in
/etc/X11/xorg.conf.d/01-resolution.conf
Xfce too is working fine for me. (Note that BusID must match the PCI
$BUS/$DEV/$FUN that QEMU assigns to virtio-gpu-pci, either
automatically, or in response to the user's "-device
virtio-gpu-pci,addr=$DEV" property.)
I guess if someone is into xserver development, this could be made a bit
more convenient, because for aarch64/KVM guests at least, virtio-gpu-pci
should be considered a primary (not secondary) graphics card.
Anyway, here's a screenshot:
http://people.redhat.com/lersek/virtio-gpu-pci-xorg-xfce.png
Thanks
Laszlo
next prev parent reply other threads:[~2016-09-01 22:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 12:49 [PATCH 00/11] OvmfPkg, ArmVirtPkg: GOP driver for the VirtIo GPU (virtio-gpu-pci) Laszlo Ersek
2016-08-19 12:49 ` [PATCH 01/11] OvmfPkg/QemuVideoDxe: don't incorrectly bind virtio-gpu-pci Laszlo Ersek
2016-08-19 12:49 ` [PATCH 02/11] OvmfPkg/Virtio10Dxe: don't bind virtio-vga Laszlo Ersek
2016-08-19 12:49 ` [PATCH 03/11] OvmfPkg/PlatformBootManagerLib: relax device class requirement for ConOut Laszlo Ersek
2016-08-19 12:49 ` [PATCH 04/11] OvmfPkg/IndustryStandard: add type definitions for the virtio GPU device Laszlo Ersek
2016-08-19 12:49 ` [PATCH 05/11] OvmfPkg/VirtioGpuDxe: introduce with Component Name 2 and Driver Binding Laszlo Ersek
2016-08-19 12:49 ` [PATCH 06/11] OvmfPkg: include VirtioGpuDxe in the platform DSC/FDF files Laszlo Ersek
2016-08-19 12:49 ` [PATCH 07/11] ArmVirtPkg/ArmVirtQemu: " Laszlo Ersek
2016-08-19 13:14 ` Ard Biesheuvel
2016-08-19 12:49 ` [PATCH 08/11] OvmfPkg/VirtioGpuDxe: initialize and tear down VirtIo GPU device Laszlo Ersek
2016-08-19 12:49 ` [PATCH 09/11] OvmfPkg/VirtioGpuDxe: provide functions for sending VirtIo GPU commands Laszlo Ersek
2016-08-19 12:49 ` [PATCH 10/11] OvmfPkg/VirtioGpuDxe: implement EFI_GRAPHICS_OUTPUT_PROTOCOL Laszlo Ersek
2016-08-19 12:49 ` [PATCH 11/11] ArmVirtPkg: remove PcdKludgeMapPciMmioAsCached Laszlo Ersek
2016-08-19 13:16 ` Ard Biesheuvel
2016-08-19 13:06 ` [PATCH 00/11] OvmfPkg, ArmVirtPkg: GOP driver for the VirtIo GPU (virtio-gpu-pci) Ard Biesheuvel
2016-08-19 14:25 ` Laszlo Ersek
2016-08-31 20:43 ` Jordan Justen
2016-09-01 7:44 ` Ard Biesheuvel
2016-09-01 16:48 ` Laszlo Ersek
2016-09-01 16:29 ` Laszlo Ersek
2016-09-01 18:03 ` Jordan Justen
2016-09-01 18:46 ` Laszlo Ersek
2016-09-01 19:52 ` Jordan Justen
2016-09-01 20:23 ` Ard Biesheuvel
2016-09-01 20:26 ` Ard Biesheuvel
2016-09-01 20:52 ` Jordan Justen
2016-09-01 20:44 ` Laszlo Ersek
2016-09-05 14:17 ` Gerd Hoffmann
2016-08-30 15:07 ` Laszlo Ersek
2016-09-01 20:32 ` Jordan Justen
2016-09-01 21:07 ` Laszlo Ersek
2016-09-01 22:02 ` Laszlo Ersek [this message]
[not found] ` <57CD6463.90903@suse.de>
2016-09-05 12:56 ` Laszlo Ersek
[not found] ` <57CD6C25.7000406@suse.de>
2016-09-05 13:17 ` Laszlo Ersek
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=f7abf2a5-4836-42c9-fffc-ad05095a7a09@redhat.com \
--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