From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastian Herbszt" Subject: Re: [Bochs-developers] [Qemu-devel] [PATCH 0/3] Add BIOS splashimage support Date: Wed, 17 Dec 2008 23:58:25 +0100 Message-ID: <4F94C0267CF24991A9DCD12549700C9D@FSCPC> References: <1229440810-12394-1-git-send-email-Laurent.Vivier@bull.net> <49480F6D.2010302@codemonkey.ws> <1229464268.26715.12.camel@frecb07144> <4948435D.1090204@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit Cc: "bochs developers" , "kvm developers" To: "Carl-Daniel Hailfinger" , Return-path: Received: from mail.gmx.net ([213.165.64.20]:41296 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752178AbYLQW7F (ORCPT ); Wed, 17 Dec 2008 17:59:05 -0500 In-Reply-To: <4948435D.1090204@gmx.net> Sender: kvm-owner@vger.kernel.org List-ID: Carl-Daniel Hailfinger wrote: > On 16.12.2008 22:51, Laurent Vivier wrote: >> But in fact, my first idea was to read the image data from the >> configuration device (which is always possible with LOGO_CMD_OFFSET), >> but when I saw how it has been done in VirtualBox, I though it was a >> good idea. Vbox used MMIO and port I/O before moving the splash support to the VGA device. > Modern x86 BIOSes read the splash screen from the BIOS ROM and the > settings from NVRAM (sometimes the BIOS ROM is used for that as well by > reflashing a sector of the ROM on every boot). I think Vbox used run-length encoding for the innotek logo bitmap. Its size was about 10 KB. If this could be used for Bochs we could put the logo into rombios32.bin and load it from the 0xe000 segment. This should be comparable to other BIOSes. - Sebastian From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LD5MD-0001QN-Aq for qemu-devel@nongnu.org; Wed, 17 Dec 2008 17:59:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LD5MA-0001Ix-6C for qemu-devel@nongnu.org; Wed, 17 Dec 2008 17:59:08 -0500 Received: from [199.232.76.173] (port=46624 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LD5M9-0001IU-Vw for qemu-devel@nongnu.org; Wed, 17 Dec 2008 17:59:06 -0500 Received: from mail.gmx.net ([213.165.64.20]:37954) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LD5M9-0002qc-AU for qemu-devel@nongnu.org; Wed, 17 Dec 2008 17:59:05 -0500 Message-ID: <4F94C0267CF24991A9DCD12549700C9D@FSCPC> From: "Sebastian Herbszt" References: <1229440810-12394-1-git-send-email-Laurent.Vivier@bull.net> <49480F6D.2010302@codemonkey.ws> <1229464268.26715.12.camel@frecb07144> <4948435D.1090204@gmx.net> In-Reply-To: <4948435D.1090204@gmx.net> Subject: Re: [Bochs-developers] [Qemu-devel] [PATCH 0/3] Add BIOS splashimage support Date: Wed, 17 Dec 2008 23:58:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Carl-Daniel Hailfinger , qemu-devel@nongnu.org Cc: bochs developers , kvm developers Carl-Daniel Hailfinger wrote: > On 16.12.2008 22:51, Laurent Vivier wrote: >> But in fact, my first idea was to read the image data from the >> configuration device (which is always possible with LOGO_CMD_OFFSET), >> but when I saw how it has been done in VirtualBox, I though it was a >> good idea. Vbox used MMIO and port I/O before moving the splash support to the VGA device. > Modern x86 BIOSes read the splash screen from the BIOS ROM and the > settings from NVRAM (sometimes the BIOS ROM is used for that as well by > reflashing a sector of the ROM on every boot). I think Vbox used run-length encoding for the innotek logo bitmap. Its size was about 10 KB. If this could be used for Bochs we could put the logo into rombios32.bin and load it from the 0xe000 segment. This should be comparable to other BIOSes. - Sebastian