From: Haiyang Zhang <haiyangz@microsoft.com>
To: Olaf Hering <olaf@aepfle.de>
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: Tue, 19 Feb 2013 17:48:39 +0000 [thread overview]
Message-ID: <1ca36b5d55c64ac6b8854c4f216ef8e5@DFM-TK5MBX15-06.exchange.corp.microsoft.com> (raw)
In-Reply-To: <20130219165118.GA17715@aepfle.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1577 bytes --]
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: Tuesday, February 19, 2013 11:51 AM
> To: Haiyang Zhang
> Cc: FlorianSchandinat@gmx.de; linux-fbdev@vger.kernel.org; KY Srinivasan;
> jasowang@redhat.com; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org
> Subject: Re: [PATCH RFC] video: Add Hyper-V Synthetic Video Frame Buffer
> Driver
>
> On Fri, Feb 15, Haiyang Zhang wrote:
>
> > @@ -508,6 +544,18 @@ static int __init vesafb_init(void)
> > int ret;
> > char *option = NULL;
> >
> > +#if IS_ENABLED(CONFIG_HYPERV_FB)
> > + /*
> > + * On Hyper-V both the emulated and synthetic video devices are
> > + * available. To avoid conflicts, we disable vesafb for the
> emulated
> > + * video if hyperv_fb is configured.
> > + */
> > + if (is_hyperv()) {
> > + pr_info("Disabled vesafb on Hyper-V.\n");
> > + return -ENODEV;
> > + }
> > +#endif
>
> What is the reason for this hook? Is it not possible to claim the
> display like its appearently done by other drivers (like radeonfb can
> take over display from vesafb)?
The emulated video device is a separate device from the synthetic video.
The synthetic driver can only take control of the synthetic video, but not
the emulated video.
Actually, we already have a similar mechanism in ata/ata_piix.c to disable
emulated IDE drive on Hyper-V, so it won't conflict with the synthetic drive.
Thanks,
- Haiyang
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-02-19 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 19:09 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 [this message]
2013-02-19 18:40 ` Olaf Hering
2013-02-19 19:04 ` Haiyang Zhang
2013-02-21 15:53 ` Olaf Hering
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=1ca36b5d55c64ac6b8854c4f216ef8e5@DFM-TK5MBX15-06.exchange.corp.microsoft.com \
--to=haiyangz@microsoft.com \
--cc=FlorianSchandinat@gmx.de \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.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
all inboxes | Powered by JetHome®