From: Gerd Hoffmann <kraxel@redhat.com>
To: linux-fbdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
kys@microsoft.com, abgupta@microsoft.com, haiyangz@microsoft.com,
jasowang@redhat.com, tomi.valkeinen@ti.com,
devel@linuxdriverproject.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH v3 0/4] hyperv-fb: add support for generation 2 virtual machines.
Date: Mon, 24 Feb 2014 13:17:07 +0000 [thread overview]
Message-ID: <1393247831-5271-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
This patch series adds support for uefi-based gen2 virtual machines to
the hyperv-fb driver. It depends on -next commit
90f3453585479d5beb75058da46eb573ced0e6ac
Patch #1 is a bugfix for 90f3453585479d5beb75058da46eb573ced0e6ac.
Patch #2 changes vmbus to properly hook the hyperv mmio area into
the linux resource management.
Patch #3 actually implements gen2 vm support for hyperv-fb, building
on the hyperv mmio support added by the other patches.
Patch #4 unregisters efifb early to make sure the framebuffer isn't used
any more while hyperv-fb initialization is in progress. This patch is
new in v2 and it fixes the hang listed as "known issue" in v1 of this
patch series.
v3 changes:
- fix a error handling bug in patch #3.
- don't include 90f3453585479d5beb75058da46eb573ced0e6ac
to avoid confusion
please apply,
Gerd
Gerd Hoffmann (4):
vmbus: add missing breaks
vmbus: use resource for hyperv mmio region
hyperv-fb: add support for generation 2 virtual machines.
hyperv-fb: kick off efifb early
K. Y. Srinivasan (1):
Drivers: hv: vmbus: Extract the mmio information from DSDT
drivers/hv/vmbus_drv.c | 51 ++++++++++++++++++++-------
drivers/video/hyperv_fb.c | 87 +++++++++++++++++++++++++++++++++--------------
include/linux/hyperv.h | 2 ++
3 files changed, 101 insertions(+), 39 deletions(-)
--
1.8.3.1
Gerd Hoffmann (4):
vmbus: add missing breaks
vmbus: use resource for hyperv mmio region
hyperv-fb: add support for generation 2 virtual machines.
hyperv-fb: kick off efifb early
drivers/hv/vmbus_drv.c | 18 ++++++----
drivers/video/hyperv_fb.c | 87 +++++++++++++++++++++++++++++++++--------------
include/linux/hyperv.h | 3 +-
3 files changed, 74 insertions(+), 34 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-02-24 13:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 13:17 Gerd Hoffmann [this message]
2014-02-24 13:17 ` [PATCH v3 1/4] vmbus: add missing breaks Gerd Hoffmann
2014-02-28 9:05 ` Tomi Valkeinen
2014-02-28 11:55 ` Gerd Hoffmann
2014-02-24 13:17 ` [PATCH v3 2/4] vmbus: use resource for hyperv mmio region Gerd Hoffmann
2014-02-24 21:57 ` KY Srinivasan
2014-02-24 13:17 ` [PATCH v3 3/4] hyperv-fb: add support for generation 2 virtual machines Gerd Hoffmann
2014-02-24 22:05 ` Haiyang Zhang
2014-02-24 13:17 ` [PATCH v3 4/4] hyperv-fb: kick off efifb early Gerd Hoffmann
2014-02-24 22:06 ` Haiyang Zhang
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=1393247831-5271-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=abgupta@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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).