[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1427353959.9779.2.camel@nilsson.home.kraxel.org>
Date: Thu, 26 Mar 2015 08:12:39 +0100
From: Gerd Hoffmann <kraxel@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: virtio-dev@...ts.oasis-open.org, Dave Airlie <airlied@...il.com>,
Dave Airlie <airlied@...hat.com>,
David Airlie <airlied@...ux.ie>,
Rusty Russell <rusty@...tcorp.com.au>,
open list <linux-kernel@...r.kernel.org>,
"open list:DRM DRIVERS" <dri-devel@...ts.freedesktop.org>,
"open list:VIRTIO CORE, NET..."
<virtualization@...ts.linux-foundation.org>,
"open list:ABI/API" <linux-api@...r.kernel.org>
Subject: Re: [PATCH] Add virtio gpu driver.
On Mi, 2015-03-25 at 18:09 +0100, Michael S. Tsirkin wrote:
> On Wed, Mar 25, 2015 at 04:37:16PM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > BTW can we teach virtio-gpu to look for framebuffer using
> > > virtio pci caps?
> >
> > The virtio-gpu driver doesn't matter much here, it doesn't use it
> > anyway.
> >
> > > Or are there limitations such as only
> > > using IO port BARs, or compatibility with
> > > BIOS code etc that limit us to specific BARs anyway?
> >
> > Yes, vgabios code needs to know. Currently it has bar #2 for the vga
> > framebuffer bar hardcoded. It's 16bit code. I don't feel like making
> > the probing more complicated ...
> >
> > cheers,
> > Gerd
>
> OK - you are saying all VGA cards use bar #2 for this
> functionality, so we are just following
> established practice here?
vgabios checks pci ids to figure. qxl+stdvga use bar #0, vmware-vga bar
#1, virtio-vga bar #2.
cheers,
Gerd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists