From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KYlkI-0005dF-C2 for qemu-devel@nongnu.org; Thu, 28 Aug 2008 13:57:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KYlkF-0005d3-Uc for qemu-devel@nongnu.org; Thu, 28 Aug 2008 13:57:21 -0400 Received: from [199.232.76.173] (port=50447 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KYlkF-0005d0-P1 for qemu-devel@nongnu.org; Thu, 28 Aug 2008 13:57:19 -0400 Received: from wf-out-1314.google.com ([209.85.200.173]:57523) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KYlkF-0008Pm-9m for qemu-devel@nongnu.org; Thu, 28 Aug 2008 13:57:19 -0400 Received: by wf-out-1314.google.com with SMTP id 27so431146wfd.4 for ; Thu, 28 Aug 2008 10:57:18 -0700 (PDT) Message-ID: Date: Thu, 28 Aug 2008 20:57:18 +0300 From: "Blue Swirl" Subject: Re: [Qemu-devel] [PATCH v3 1/6] Use IO port for qemu<->guest BIOS communication. In-Reply-To: <20080828165237.22851.1532.stgit@gleb-debian.qumranet.com.qumranet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080828165232.22851.77678.stgit@gleb-debian.qumranet.com.qumranet.com> <20080828165237.22851.1532.stgit@gleb-debian.qumranet.com.qumranet.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 8/28/08, Gleb Natapov wrote: > Use PIO to get configuration info between qemu process and guest BIOS. Looking good ;-) Sparc targets need these firmware_abi.h fields, and probably other targets too: uint64_t RAM0_size; uint64_t kernel_image; uint64_t kernel_size; uint64_t cmdline; uint64_t cmdline_size; uint16_t graphic_flags; uint8_t nb_cpus; uint8_t nboot_devices; uint8_t boot_devices[0x10]; Maybe not all targets want these: uint16_t width; uint16_t height; uint16_t depth; But before keys for these are added, it's not possible to migrate Sparc targets to the new system. So should these be global?