From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOxVv-0000ux-1z for qemu-devel@nongnu.org; Thu, 09 Jul 2009 13:34:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOxVq-0000jr-As for qemu-devel@nongnu.org; Thu, 09 Jul 2009 13:34:30 -0400 Received: from [199.232.76.173] (port=39976 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOxVq-0000ja-49 for qemu-devel@nongnu.org; Thu, 09 Jul 2009 13:34:26 -0400 Received: from mx20.gnu.org ([199.232.41.8]:28883) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOxVp-0006WH-RH for qemu-devel@nongnu.org; Thu, 09 Jul 2009 13:34:25 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MOxVo-0000cB-Ur for qemu-devel@nongnu.org; Thu, 09 Jul 2009 13:34:25 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH] Drop roms from standard build Date: Thu, 9 Jul 2009 18:34:20 +0100 References: <4A559842.7000404@web.de> <200907091808.06764.paul@codesourcery.com> <4A5624D6.8060007@us.ibm.com> In-Reply-To: <4A5624D6.8060007@us.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907091834.22163.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Jan Kiszka , qemu-devel@nongnu.org, Alexander Graf > > Also, x86 is only one of many targets qemu supports. If you're serious > > about rebuilding roms as standard, then at bare minimum you need to > > handle sparc and ppc as well as x86. > > Yup. That's why we need to probe for toolchains in order to determine > whether roms can be built. If you're a developer making changes to > OpenBIOS, clearly you are going to have the appropriate tool chains > installed. IMO a developer changes to a rom is a special case. If you're arguing that roms should be built by default, for everyone, then I disagree and don't think this is feasible. Most users simply don't have the prerequisites, and don't want to have to cofigure everything even when they do. If you care about this (for reproducibility or licencing reasons) then it should be all or nothing. I don't buy "It works for x86-on-x86 most of the time" as a valid argument for anything. We either build things by default, or we include binaries, not both. If you're talking about developers modifying the roms, then most of the arguments above still apply. Chances are you're only actually interested in one rom anyway, so building it separately really isn't significant extra hassle. Having everything in one source tree maybe makes sense. Except that most roms are already used by several projects. What you really want is to coordinate releases with the upstream maintainers, having a qemu branck/fork if it's really that hard to get changes integrated back. In the case of the pc-bios it probably wants to be split into a sparate project, rather than being part of bochs. Paul