[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5746838b7654aac98a5753d669196b4@SN2PR03MB061.namprd03.prod.outlook.com>
Date: Mon, 7 Oct 2013 17:12:53 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Gerd Hoffmann <kraxel@...hat.com>
CC: Haiyang Zhang <haiyangz@...rosoft.com>,
Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
"open list:Hyper-V CORE AND..." <devel@...uxdriverproject.org>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] hyperv-fb: add pci stub
> -----Original Message-----
> From: Gerd Hoffmann [mailto:kraxel@...hat.com]
> Sent: Sunday, October 06, 2013 11:51 PM
> To: KY Srinivasan
> Cc: Haiyang Zhang; Jean-Christophe Plagniol-Villard; Tomi Valkeinen; open
> list:Hyper-V CORE AND...; open list:FRAMEBUFFER LAYER; open list
> Subject: Re: [PATCH 1/2] hyperv-fb: add pci stub
>
> 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).
We are going to fix this as we move this code to run on our UEFI firmware.
Regards,
K. Y
Powered by blists - more mailing lists