From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C44v0-0003AS-El for qemu-devel@nongnu.org; Sun, 05 Sep 2004 17:51:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C44uy-0003A3-Lt for qemu-devel@nongnu.org; Sun, 05 Sep 2004 17:51:25 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C44uy-0003A0-JP for qemu-devel@nongnu.org; Sun, 05 Sep 2004 17:51:24 -0400 Received: from [64.233.170.199] (helo=mproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C44pg-0007kO-2R for qemu-devel@nongnu.org; Sun, 05 Sep 2004 17:45:56 -0400 Received: by mproxy.gmail.com with SMTP id 77so226682rnk for ; Sun, 05 Sep 2004 14:45:49 -0700 (PDT) Message-ID: <5393dd63040905144553b397be@mail.gmail.com> Date: Sun, 5 Sep 2004 23:45:49 +0200 From: Patrick Mauritz Subject: Re: [Qemu-devel] Sparc system emulation in progress In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Reply-To: Patrick Mauritz , 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 Sun, 05 Sep 2004 23:11:43 +0200, Blue Swirl wrote: > Thank you for the tip, but Openbios does not support Sparc. it's pretty portable, actually, for emulation it's especially easy to adapt (as you can avoid the lowlevel init stuff - no-one cares for that part as long as the state is right, which you can accomplish differently in an emulator). what do you need - a firmware image built for SPARC for a certain start address (easy) and fcode images to initialize the "hardware" (more work), anything else? for the fcode images, the interfaces to use is important. I guess you want to emulate some real chipsets, as most operating systems don't rely on the services of openfirmware at all, not even as fallback - which is a shame. looking at proll, it seems like linux is a bad choice for the first iteration of a port as it seems to rely on inofficial firmware properties - netbsd should be more compliant patrick mauritz