From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (using TLSv1 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9BC1F1A1E77 for ; Thu, 1 Sep 2016 12:52:51 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP; 01 Sep 2016 12:52:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,268,1470726000"; d="scan'208";a="1023863209" Received: from danyzest-mobl.amr.corp.intel.com (HELO localhost) ([10.252.141.10]) by orsmga001.jf.intel.com with ESMTP; 01 Sep 2016 12:52:50 -0700 MIME-Version: 1.0 To: Laszlo Ersek , Message-ID: <147275957055.21562.7750188759462698423@jljusten-ivb> From: Jordan Justen In-Reply-To: <0500cc50-86f9-ab97-f22d-012ac1857ad0@redhat.com> Cc: "Ard Biesheuvel" , "edk2-devel-01" References: <20160819124932.29711-1-lersek@redhat.com> <147267618723.12178.11385591212119668150@jljusten-ivb> <2c5b6038-a51a-9206-392b-d391c0aabf51@redhat.com> <147275300806.20661.4606850370467291385@jljusten-ivb> <0500cc50-86f9-ab97-f22d-012ac1857ad0@redhat.com> User-Agent: alot/0.3.7 Date: Thu, 01 Sep 2016 12:52:50 -0700 Subject: Re: [PATCH 00/11] OvmfPkg, ArmVirtPkg: GOP driver for the VirtIo GPU (virtio-gpu-pci) X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 19:52:51 -0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 2016-09-01 11:46:04, Laszlo Ersek wrote: > On 09/01/16 20:03, Jordan Justen wrote: > = > > I think there would be value to have a non-VGA device that could still > > configure a simple framebuffer. VGA does bring a fair amount of other > > baggage. > = > Ah, I see your point. You distinguish "VGA" from "non-VGA device with > framebuffer". > = > For this discussion however, this distinction makes no difference. The > suggested "non-VGA device with framebuffer" would be broken exactly the > same way. In other words, it's not the "other baggage" that is broken, > it is the framebuffer. > This is only focusing on the current ARM issue. I'm just pointing out that I think virtio gpu without VGA, but with a framebuffer could be useful on IA32/X64 as well. 1. You don't have to deal with the PCI bus 2. The OS re-enumerating the PCI bus would not break the framebuffer Is there no chance that ARM KVM might someday also be able to support a framebuffer? Obviously this is not too important for IA32/X64 OVMF, because we have reasonable alternatives. But, it seems like virtio gpu could be a significantly better option for IA32/X64 OVMF if an optional framebuffer was possible. -Jordan