From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDr4S-0006O0-Rh for qemu-devel@nongnu.org; Thu, 26 Nov 2009 22:00:32 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDr4P-0006Lf-1k for qemu-devel@nongnu.org; Thu, 26 Nov 2009 22:00:32 -0500 Received: from [199.232.76.173] (port=41774 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDr4O-0006Lc-Jk for qemu-devel@nongnu.org; Thu, 26 Nov 2009 22:00:28 -0500 Received: from mail2.shareable.org ([80.68.89.115]:43011) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NDr4O-0006bt-Dt for qemu-devel@nongnu.org; Thu, 26 Nov 2009 22:00:28 -0500 Date: Fri, 27 Nov 2009 03:00:23 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios Message-ID: <20091127030023.GC6094@shareable.org> References: <11090DAABE9449F7B5D1415C45F8F411@FSCPC> <20091123194307.GC13854@redhat.com> <2D659FA33BF64C419243FD76049AFD33@FSCPC> <20091124062810.GZ2999@redhat.com> <20091124143812.GA27783@shareable.org> <20091124144044.GJ2999@redhat.com> <20091125060951.GA17203@shareable.org> <20091125122039.GM2999@redhat.com> <20091125153116.GA30957@morn.localdomain> <168FD1E43DF64B0DB0942A6EC0BD3A62@FSCPC> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <168FD1E43DF64B0DB0942A6EC0BD3A62@FSCPC> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastian Herbszt Cc: Kevin O'Connor , qemu-devel@nongnu.org, Gleb Natapov Sebastian Herbszt wrote: > >We could have qemu do a soft reset (not reload rom) on a triple fault > >or keyboard controller reset, and then have SeaBIOS request a hard > >reset (have qemu reload rom) if it detects a soft reset that is not a > >"resume" request. > > > >I'm also not sure what qemu does today. > > I don't think such an interface would add a long time benefit and > would prefer a proper solution which will not tie seabios even more > to qemu. One day it might be possible to run a commercial BIOS on > qemu, just like it is possible on Bochs. Adding this interface > might prevent that. What does a real BIOS on real hardware do? Do real BIOSes make a decision as described above, and we're just assuming they don't? One way to answer may be: On a real PC with i440FX, what kind of reset are the different reset methods (triple fault, keyboard etc.) normally configured to do? IIRC, HIMEM.SYS in DOS must use at least one of the switch-to-real-mode methods to work, and that driver is needed by Windows 3/3.11/95/98/ME, but I'm a bit vague on the details. -- Jamie