From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:56936) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gosyz-00038J-Qd for qemu-devel@nongnu.org; Wed, 30 Jan 2019 11:45:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gosyz-00051M-6r for qemu-devel@nongnu.org; Wed, 30 Jan 2019 11:45:01 -0500 References: <87y378n5iy.fsf@dusky.pond.sub.org> <871s4uobf0.fsf@dusky.pond.sub.org> From: Laszlo Ersek Message-ID: <75629302-84bb-ba19-cb2c-5edc34cffadb@redhat.com> Date: Wed, 30 Jan 2019 17:44:52 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Configuring pflash devices for OVMF firmware List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Markus Armbruster Cc: Libvirt , Peter Krempa , QEMU Developers , Qemu-block On 01/30/19 16:24, Peter Maydell wrote: > Well, nobody who does anything with x86 has cared enough to > make the pflash implementation actually correct. I feel sort of included under this umbrella, so: I haven't been aware of any particular pflash implementation errors. I "didn't care" because it "worked fine" as much as I could tell. Thanks Laszlo