From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LnS5T-0007Ix-5O for qemu-devel@nongnu.org; Sat, 28 Mar 2009 02:32:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LnS5O-00077b-F0 for qemu-devel@nongnu.org; Sat, 28 Mar 2009 02:32:10 -0400 Received: from [199.232.76.173] (port=46706 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LnS5O-00077H-3i for qemu-devel@nongnu.org; Sat, 28 Mar 2009 02:32:06 -0400 Received: from mail-bw0-f172.google.com ([209.85.218.172]:59121) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LnS5N-0008J2-Jj for qemu-devel@nongnu.org; Sat, 28 Mar 2009 02:32:05 -0400 Received: by bwz20 with SMTP id 20so1161753bwz.34 for ; Fri, 27 Mar 2009 23:32:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <49CD42A8.5010602@earthlink.net> References: <49C8BD24.3080803@earthlink.net> <49CD42A8.5010602@earthlink.net> Date: Sat, 28 Mar 2009 08:32:04 +0200 Message-ID: From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: r6777 breaks running sun OPB images Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Robert Reif Cc: qemu-devel@nongnu.org, aurelien@aurel32.net, Peter On 3/27/09, Robert Reif wrote: > Blue Swirl wrote: > > > On 3/24/09, Robert Reif wrote: > > > > > > > Sparc SS5-170 Open Boot PROM images run differently after this patch. > > > > > > In particular, POST is no longer run. I can provide the PROM image if > > > necessary for testing. > > > > > > Can we make NVRAM environment variables OBP compatible or persistent > some > > > how so we can run either OBP or OpenBIOS? > > > > > > > > > > Maybe, if there is a good spec for the variable format and other > structures. > > > > > > > I think adding a persistent mode to NVRAM so it's contents can be either > generated for OpenBIOS like it is now or read from and written to a file > based on what Open Boot PROM does. That way you don't need to add a new > mode to Open BIOS and you don't need to know what Open Boot PROM does. That would work too. Bonus points offered for making the specific device state save/load stuff generic (available for all devices) using both savevm/loadvm and raw formats.