[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1427895778.6445.13.camel@nilsson.home.kraxel.org>
Date: Wed, 01 Apr 2015 15:42:58 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: dri-devel@...ts.freedesktop.org, virtio-dev@...ts.oasis-open.org,
airlied@...il.com, airlied@...hat.com,
David Airlie <airlied@...ux.ie>,
Rusty Russell <rusty@...tcorp.com.au>,
open list <linux-kernel@...r.kernel.org>,
"open list:VIRTIO CORE, NET..."
<virtualization@...ts.linux-foundation.org>
Subject: Re: [PATCH v2 4/4] Add virtio-vga bits.
On Mi, 2015-04-01 at 15:26 +0200, Michael S. Tsirkin wrote:
> On Wed, Apr 01, 2015 at 03:15:30PM +0200, Gerd Hoffmann wrote:
> > +static void virtio_pci_kick_out_firmware_fb(struct pci_dev *pci_dev)
> > +{
> > + struct apertures_struct *ap;
> > + bool primary;
> > +
> > + ap = alloc_apertures(1);
> > + if (!ap)
> > + return;
> > +
> > + ap->ranges[0].base = pci_resource_start(pci_dev, 2);
> > + ap->ranges[0].size = pci_resource_len(pci_dev, 2);
>
> I thought you mentioned it's better to switch to a different BAR
> to be compatible with stdvga?
Indeed, thats why the cover letter lists this as todo item, because it
isn't sorted yet.
Need to figure a sane way to handle this on the host side. Current plan
is trying to make virtio_pci_device_plugged() configurable without
making things too messy.
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