From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] realemu
Date: Wed, 2 Mar 2011 02:35:44 +0100 [thread overview]
Message-ID: <28a5a9ad234d733f7758054ba3b7171a@gmx.de> (raw)
In-Reply-To: <c90065aa10d96ec87012d17cc1d47174@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
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
[-- Attachment #2: Type: message/rfc822, Size: 2698 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] realemu
Date: Tue, 1 Mar 2011 20:16:25 -0500
Message-ID: <c90065aa10d96ec87012d17cc1d47174@brasstown.quanstro.net>
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
next prev parent reply other threads:[~2011-03-02 1:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 0:22 cinap_lenrek
2011-03-02 0:30 ` erik quanstrom
2011-03-02 0:49 ` Gorka Guardiola
2011-03-02 0:58 ` erik quanstrom
2011-03-02 1:08 ` cinap_lenrek
2011-03-02 1:06 ` cinap_lenrek
2011-03-02 1:16 ` erik quanstrom
2011-03-02 1:35 ` cinap_lenrek [this message]
2011-03-02 1:40 ` erik quanstrom
2011-03-02 1:52 ` ron minnich
2011-03-02 3:08 ` Venkatesh Srinivas
2011-03-02 3:31 ` erik quanstrom
2011-03-02 5:42 ` cinap_lenrek
2011-03-02 1:43 ` cinap_lenrek
2011-03-02 1:47 ` erik quanstrom
2011-03-06 5:39 ` [9fans] rc and pmake yard-ape
2011-03-02 1:17 ` [9fans] realemu cinap_lenrek
2011-03-02 1:18 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28a5a9ad234d733f7758054ba3b7171a@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).