[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1427443706.22166.10.camel@nilsson.home.kraxel.org>
Date: Fri, 27 Mar 2015 09:08:26 +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: [virtio-dev] Re: [PATCH] Add virtio gpu driver.
Hi,
> >
> > Completely different thing crossing my mind: I think we can make
> > virtio-vga fully compatible with stdvga. stdvga has two bars, memory
> > (#0) and mmio (#2). We can make the mmio bar larger and place all the
> > virtio regions there.
> >
>
> Full compatibility with some standard sounds like a better motivation,
> yes.
Ok, I'll look into it.
> > I think in any case I'll go split off the vga compatibility bits to a
> > different patch (and possible a separate patch series).
> >
> > cheers,
> > Gerd
>
> Will you still need me to change core to claim specific memory only?
That would be great, yes. The resource conflict with vesafb/efifb will
stay no matter how we design the pci resource layout of virtio-vga.
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