From: Gerd Hoffmann <kraxel@redhat.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
"open list:Hyper-V CORE AND..." <devel@linuxdriverproject.org>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] hyperv-fb: add pci stub
Date: Mon, 07 Oct 2013 06:50:33 +0000 [thread overview]
Message-ID: <1381128633.13574.3.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <465ef0cb45e04bcc94c4788c0d930c4d@SN2PR03MB061.namprd03.prod.outlook.com>
On Mi, 2013-10-02 at 14:29 +0000, KY Srinivasan wrote:
>
> > This patch adds a pci stub driver to hyper-fb. The hyperv framebuffer
> > driver will bind to the pci device then, so linux kernel and userspace
> > know there is a proper kernel driver for the device active. lspci shows
> > this for example:
> Gerd,
>
> Thanks for doing this. This certainly will address some of the issues that are reported. I do have a question though - how would this work if we don't have PCI bus in the guest.
The hyperv framebuffer driver wouldn't work in the first place then as
it looks up the framebuffer address in pci config space (see hvfb_getmem
function).
cheers,
Gerd
next prev parent reply other threads:[~2013-10-07 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 11:55 [PATCH 1/2] hyperv-fb: add pci stub Gerd Hoffmann
2013-10-02 11:55 ` [PATCH 2/2] hyperv-fb: add blanking support Gerd Hoffmann
2013-10-02 20:43 ` Haiyang Zhang
2013-10-02 14:29 ` [PATCH 1/2] hyperv-fb: add pci stub KY Srinivasan
2013-10-07 6:50 ` Gerd Hoffmann [this message]
2013-10-07 17:12 ` KY Srinivasan
2013-10-08 8:41 ` Gerd Hoffmann
2013-10-08 14:48 ` KY Srinivasan
2013-10-02 20:42 ` Haiyang Zhang
2013-10-09 9:53 ` Tomi Valkeinen
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=1381128633.13574.3.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--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).