From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] realemu
Date: Wed, 2 Mar 2011 02:06:29 +0100 [thread overview]
Message-ID: <423df806c28872b15102d5148d6fdb8a@gmx.de> (raw)
In-Reply-To: <35a1bf3e40be73448a06094f4fdb169a@ladd.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
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.
--
cinap
[-- Attachment #2: Type: message/rfc822, Size: 3890 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] realemu
Date: Tue, 1 Mar 2011 19:30:05 -0500
Message-ID: <35a1bf3e40be73448a06094f4fdb169a@ladd.quanstro.net>
On Tue Mar 1 19:23:42 EST 2011, cinap_lenrek@gmx.de wrote:
> completed realmode emulator that is to be used with aux/vga -m vesa ...
> to enable the graphics card thru vesa bios in an attempt to make 8i
> work (thanks russ ;-)).
>
> tarball can be found in /n/sources/contrib/cinap_lenrek/realemu.tgz
>
> needs the patch /n/sources/patch/vesa-softscreen-resize applied as the
> vgavesa driver has to go thru the emulated /dev/realmode instead of
> the short path by calling realmode() directly.
>
> more details are in the notes file.
>
> there is a incomplete list of graphics cards this was tested on in the
> vgalist file included in the tarball. (have like 5 working pci graphics
> cards here that i'm too lazy to hookup again to get the vid/did numbers)
>
> you might hit unimplemented instructions or code spinning in endless
> loops due to lack of proper system port emulation (i just return 0 on IN[BWL]
> instructions for restricted ports right now).
i'm sorry i've forgotten. what's the problem with unemulated vesa?
- erik
next prev parent reply other threads:[~2011-03-02 1:06 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 [this message]
2011-03-02 1:16 ` erik quanstrom
2011-03-02 1:35 ` cinap_lenrek
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=423df806c28872b15102d5148d6fdb8a@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).