public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@csgraf.de>
To: u-boot@lists.denx.de
Cc: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>,
	Simon Glass <sjg@chromium.org>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	Bin Meng <bmeng.cn@gmail.com>, Asherah Connor <ashe@kivikakk.ee>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Anatolij Gustschin <agust@denx.de>
Subject: [PATCH 0/4] Add support for QEMU's ramfb display
Date: Sun, 27 Feb 2022 15:40:39 +0100	[thread overview]
Message-ID: <20220227144043.37359-1-agraf@csgraf.de> (raw)

QEMU implements multiple ways to expose graphics output to the virt
machine, but most of them are incompatible with hardware virtualization.

The one that does work reliably is ramfb. It's a very simple mechanism
in which the guest reserves a memory region for the frame buffer and then
notifies the host about its location and properties. The host then just
displays the contents of the frame buffer on screen.

This patch set adds support to drive the ramfb device in our QEMU arm
targets. Theoretically, it should work as is with any of the other
architectures as well though.

With this driver, we have a very simple, KVM compatible way to expose
GOP via UEFI to payloads and thus enable development and testing of
graphical OS functionality with QEMU's -M virt.

Alexander Graf (4):
  qfw: Add WRITE definition
  ramfb: Add driver for ramfb display
  qfw: Spawn ramfb device if its file is present
  qemu-arm*: Enable ramfb by default

 arch/arm/Kconfig                    |   4 ++
 board/emulation/qemu-arm/qemu-arm.c |  14 ++++
 drivers/misc/qfw.c                  |  23 ++++++
 drivers/video/Kconfig               |   8 +++
 drivers/video/MAINTAINERS           |   4 ++
 drivers/video/Makefile              |   1 +
 drivers/video/ramfb.c               | 104 ++++++++++++++++++++++++++++
 include/configs/qemu-arm.h          |   9 +++
 include/qfw.h                       |   1 +
 9 files changed, 168 insertions(+)
 create mode 100644 drivers/video/MAINTAINERS
 create mode 100644 drivers/video/ramfb.c

-- 
2.32.0


             reply	other threads:[~2022-02-27 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 14:40 Alexander Graf [this message]
2022-02-27 14:40 ` [PATCH 1/4] qfw: Add WRITE definition Alexander Graf
2022-03-12  2:25   ` Simon Glass
2022-02-27 14:40 ` [PATCH 2/4] ramfb: Add driver for ramfb display Alexander Graf
2022-03-12  2:25   ` Simon Glass
2022-02-27 14:40 ` [PATCH 3/4] qfw: Spawn ramfb device if its file is present Alexander Graf
2022-02-27 14:40 ` [PATCH 4/4] qemu-arm*: Enable ramfb by default Alexander Graf
2022-02-27 15:35 ` [PATCH 0/4] Add support for QEMU's ramfb display Heinrich Schuchardt
2022-02-27 17:05   ` Alexander Graf
2022-02-27 17:03 ` [PATCH 5/5] qemu-riscv: Enable ramfb by default Alexander Graf

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=20220227144043.37359-1-agraf@csgraf.de \
    --to=agraf@csgraf.de \
    --cc=agust@denx.de \
    --cc=ashe@kivikakk.ee \
    --cc=bmeng.cn@gmail.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=sjg@chromium.org \
    --cc=tuomas.tynkkynen@iki.fi \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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