From: Olaf Hering <olaf@aepfle.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "FlorianSchandinat@gmx.de" <FlorianSchandinat@gmx.de>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH RFC] video: Add Hyper-V Synthetic Video Frame Buffer Driver
Date: Thu, 21 Feb 2013 15:53:59 +0000 [thread overview]
Message-ID: <20130221155359.GA28637@aepfle.de> (raw)
In-Reply-To: <7267f77544c24531b8fcccc2192b9f48@DFM-TK5MBX15-06.exchange.corp.microsoft.com>
On Tue, Feb 19, Haiyang Zhang wrote:
> > I havent read the vesafb code, but I think it can kind of give up the
> > hardware, something ata_piix can not do.
>
> In my test, the vesafb doesn't automatically give up the emulated video device,
> unless I add the DMI based mechanism to let it exit on Hyper-V.
From reading the code, it seems to do that via
do_remove_conflicting_framebuffers(). hypervfb does not set apertures
etc, so that function is a noop.
My point is that with this new driver distro kernel will have no console
output until hypervfb is loaded. On native hardware there is at least
vesafb which can display something until initrd is running. So if the
hypervisor allows that hypervfb can shutdown the emulated vesa hardware
then it should do that.
Olaf
next prev parent reply other threads:[~2013-02-21 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 18:48 [PATCH RFC] video: Add Hyper-V Synthetic Video Frame Buffer Driver Haiyang Zhang
2013-02-17 14:32 ` Olaf Hering
2013-02-17 19:10 ` Haiyang Zhang
2013-02-18 10:29 ` Geert Uytterhoeven
2013-02-18 16:09 ` Haiyang Zhang
2013-02-19 16:51 ` Olaf Hering
2013-02-19 17:48 ` Haiyang Zhang
2013-02-19 18:40 ` Olaf Hering
2013-02-19 19:04 ` Haiyang Zhang
2013-02-21 15:53 ` Olaf Hering [this message]
2013-02-22 4:11 ` Haiyang Zhang
2013-02-28 15:16 ` Olaf Hering
2013-02-28 17:56 ` 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=20130221155359.GA28637@aepfle.de \
--to=olaf@aepfle.de \
--cc=FlorianSchandinat@gmx.de \
--cc=devel@linuxdriverproject.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 \
/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).