From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753548AbbCYPha (ORCPT ); Wed, 25 Mar 2015 11:37:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45135 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752964AbbCYPh2 (ORCPT ); Wed, 25 Mar 2015 11:37:28 -0400 Message-ID: <1427297836.23304.29.camel@nilsson.home.kraxel.org> Subject: 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: Wed, 25 Mar 2015 16:37:16 +0100 In-Reply-To: <20150325162246-mutt-send-email-mst@redhat.com> References: <1427213239-8775-1-git-send-email-kraxel@redhat.com> <20150324171255-mutt-send-email-mst@redhat.com> <1427295121.23304.5.camel@nilsson.home.kraxel.org> <20150325162246-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, > 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