From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <28a5a9ad234d733f7758054ba3b7171a@gmx.de> To: 9fans@9fans.net Date: Wed, 2 Mar 2011 02:35:44 +0100 From: cinap_lenrek@gmx.de In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-sfksrwdczchcwdpwjlbbwofxmz" Subject: Re: [9fans] realemu Topicbox-Message-UUID: b6398d94-ead6-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-sfksrwdczchcwdpwjlbbwofxmz Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit yes, i had one that did this as its first thing then chained into some other bios call. i have to look... i might still have the trace log. i do no attempt in detecting bad stuff. its perfectly valid to enable interrupts in the emulator... there are no interrupts in the virtual machine right now (might change if i implement pit timer). the list is just the stuff that was tested with the emulation and worked enableing video. might be a good idea to add "aggressive" bios behaviour in the description. -- cinap --upas-sfksrwdczchcwdpwjlbbwofxmz Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-bounces@9fans.net> Delivered-To: GMX delivery to cinap_lenrek@gmx.de Received: (qmail invoked by alias); 02 Mar 2011 01:21:39 -0000 Received: from mail.9fans.net (EHLO mail.9fans.net) [67.207.142.3] by mx0.gmx.net (mx091) with SMTP; 02 Mar 2011 02:21:39 +0100 Received: from localhost ([127.0.0.1] helo=[67.207.142.3]) by mail.9fans.net with esmtp (Exim 4.71) (envelope-from <9fans-bounces@9fans.net>) id 1PuasH-0003Wo-87; Wed, 02 Mar 2011 01:29:09 +0000 Received: from ladd.quanstro.net ([69.55.170.73]) by mail.9fans.net with esmtp (Exim 4.71) (envelope-from ) id 1PuasE-0003We-6f for 9fans@9fans.net; Wed, 02 Mar 2011 01:29:06 +0000 From: erik quanstrom Date: Tue, 1 Mar 2011 20:16:25 -0500 To: 9fans@9fans.net Message-ID: In-Reply-To: <423df806c28872b15102d5148d6fdb8a@gmx.de> References: <423df806c28872b15102d5148d6fdb8a@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] realemu X-BeenThere: 9fans@9fans.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces@9fans.net Errors-To: 9fans-bounces@9fans.net X-GMX-Antivirus: 0 (no virus found) X-GMX-Antispam: 0 (Sender is in whitelist: quanstro@quanstro.net); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnShX0FizdQl9RFZ0GCoYzuI/5tuj+6f1Bo33qJ FpAu0p8VGnOp3+cZQ==V1; On Tue Mar 1 20:07:19 EST 2011, cinap_lenrek@gmx.de wrote: > the real realmode is shoot and pray. it might just crash the machine > or do wired things like reenable interrupts or even try to switch > itself to protected mode. > > with realemu, you might get a messed up screen, but plan9 is still > running. in case the vesa bios did wired stuff that caused plan9 to > crash before, it might now work with realemu. have you caught any bioses reenabling interrupts or doing other things like that? what's the strategy for detecting vesa bios "doing bad things"? is the included list of video cards a list of cards that do not work with the regular realmode but do work with emulated real mode? - erik --upas-sfksrwdczchcwdpwjlbbwofxmz--