From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 1/2] stubs: add ramfb
Date: Mon, 10 Sep 2018 08:43:39 +0200 [thread overview]
Message-ID: <20180910064340.30745-2-kraxel@redhat.com> (raw)
In-Reply-To: <20180910064340.30745-1-kraxel@redhat.com>
Needed to make sure code using ramfb (vfio) compiles properly even on
platforms without fw_cfg (and therefore no ramfb) support.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
stubs/ramfb.c | 13 +++++++++++++
stubs/Makefile.objs | 1 +
2 files changed, 14 insertions(+)
create mode 100644 stubs/ramfb.c
diff --git a/stubs/ramfb.c b/stubs/ramfb.c
new file mode 100644
index 0000000000..48143f3354
--- /dev/null
+++ b/stubs/ramfb.c
@@ -0,0 +1,13 @@
+#include "qemu/osdep.h"
+#include "qapi/error.h"
+#include "hw/display/ramfb.h"
+
+void ramfb_display_update(QemuConsole *con, RAMFBState *s)
+{
+}
+
+RAMFBState *ramfb_setup(Error **errp)
+{
+ error_setg(errp, "ramfb support not available");
+ return NULL;
+}
diff --git a/stubs/Makefile.objs b/stubs/Makefile.objs
index 53d3f32cb2..5dd0aeeec6 100644
--- a/stubs/Makefile.objs
+++ b/stubs/Makefile.objs
@@ -43,3 +43,4 @@ stub-obj-y += xen-common.o
stub-obj-y += xen-hvm.o
stub-obj-y += pci-host-piix.o
stub-obj-y += ram-block.o
+stub-obj-y += ramfb.o
--
2.9.3
next prev parent reply other threads:[~2018-09-10 6:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 6:43 [Qemu-devel] [PATCH 0/2] hw/vfio/display: add ramfb support Gerd Hoffmann
2018-09-10 6:43 ` Gerd Hoffmann [this message]
2018-09-10 6:43 ` [Qemu-devel] [PATCH 2/2] " Gerd Hoffmann
2018-09-10 18:54 ` Alex Williamson
2018-09-11 4:38 ` Gerd Hoffmann
2018-09-12 17:13 ` Alex Williamson
2018-09-14 10:50 ` Gerd Hoffmann
2018-09-14 14:19 ` [Qemu-devel] [libvirt] " Erik Skultety
2018-09-14 15:16 ` Alex Williamson
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=20180910064340.30745-2-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).