From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753759AbbC0IIq (ORCPT ); Fri, 27 Mar 2015 04:08:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38631 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751823AbbC0IIl (ORCPT ); Fri, 27 Mar 2015 04:08:41 -0400 Message-ID: <1427443706.22166.10.camel@nilsson.home.kraxel.org> Subject: Re: [virtio-dev] Re: [PATCH] Add virtio gpu driver. From: Gerd Hoffmann To: "Michael S. Tsirkin" Cc: virtio-dev@lists.oasis-open.org, Dave Airlie , Dave Airlie , David Airlie , Rusty Russell , open list , "open list:DRM DRIVERS" , "open list:VIRTIO CORE, NET..." , "open list:ABI/API" Date: Fri, 27 Mar 2015 09:08:26 +0100 In-Reply-To: <20150326174401-mutt-send-email-mst@redhat.com> References: <20150325162246-mutt-send-email-mst@redhat.com> <1427297836.23304.29.camel@nilsson.home.kraxel.org> <20150325180721-mutt-send-email-mst@redhat.com> <1427353959.9779.2.camel@nilsson.home.kraxel.org> <20150326091545-mutt-send-email-mst@redhat.com> <1427359367.9779.9.camel@nilsson.home.kraxel.org> <20150326095736-mutt-send-email-mst@redhat.com> <1427369923.9779.18.camel@nilsson.home.kraxel.org> <20150326124751-mutt-send-email-mst@redhat.com> <1427382436.8786.15.camel@nilsson.home.kraxel.org> <20150326174401-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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