From: Ahmad Fatoum <ahmad@a3f.at>
To: barebox@lists.infradead.org
Cc: Adrian Negreanu <adrian.negreanu@nxp.com>, Ahmad Fatoum <ahmad@a3f.at>
Subject: [PATCH v2 0/4] video: add support for QEMU ramfb
Date: Mon, 30 Jan 2023 08:27:03 +0100 [thread overview]
Message-ID: <20230130072707.2423294-1-ahmad@a3f.at> (raw)
QEMU's ramfb is a very simple Qemu fw_cfg protocol, where the guest
need only write a video settings structure to /etc/ramfb to get
DMA from the framebuffer working. Add a driver for this on top
of a newly added character device interface.
Adrian Negreanu (1):
video: add support for QEMU ramfb
Ahmad Fatoum (3):
fs: devfs: implement cdev_fdopen
asm-generic: avoid compiler warnings due to PCI_IOBASE
firmware: add QEMU FW CFG driver
drivers/firmware/Kconfig | 10 +
drivers/firmware/Makefile | 1 +
drivers/firmware/qemu_fw_cfg.c | 307 +++++++++++++++++++++++++++++++
drivers/video/Kconfig | 6 +
drivers/video/Makefile | 1 +
drivers/video/ramfb.c | 191 +++++++++++++++++++
fs/devfs-core.c | 20 ++
include/asm-generic/io.h | 3 +-
include/driver.h | 1 +
include/filetype.h | 1 +
include/uapi/linux/qemu_fw_cfg.h | 100 ++++++++++
11 files changed, 640 insertions(+), 1 deletion(-)
create mode 100644 drivers/firmware/qemu_fw_cfg.c
create mode 100644 drivers/video/ramfb.c
create mode 100644 include/uapi/linux/qemu_fw_cfg.h
--
2.38.1
next reply other threads:[~2023-01-30 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 7:27 Ahmad Fatoum [this message]
2023-01-30 7:27 ` [PATCH v2 1/4] fs: devfs: implement cdev_fdopen Ahmad Fatoum
2023-01-30 7:27 ` [PATCH v2 2/4] asm-generic: avoid compiler warnings due to PCI_IOBASE Ahmad Fatoum
2023-01-30 7:27 ` [PATCH v2 3/4] firmware: add QEMU FW CFG driver Ahmad Fatoum
2023-01-30 7:27 ` [PATCH v2 4/4] video: add support for QEMU ramfb Ahmad Fatoum
2023-01-31 8:19 ` [PATCH v2 0/4] " Sascha Hauer
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=20230130072707.2423294-1-ahmad@a3f.at \
--to=ahmad@a3f.at \
--cc=adrian.negreanu@nxp.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox