From: cinap_lenrek@gmx.de
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] realemu update
Date: Sun, 6 Mar 2011 19:48:03 +0100 [thread overview]
Message-ID: <08d2ecf0b69e5840218c2803692a5a5a@gmx.de> (raw)
In-Reply-To: <a3c9b4d5c5119c1f3a4a8d9debb28b08@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
yes, this started as 8i from russ. it was renamed to realemu after i
made it into a fileserver providing /dev/realmode and
/dev/realmodemem. this way i dont have to reimplement aux/vga's vesa
code and it can be used as drop in replacement. (just start it before
running aux/vga)
mkfile is fixed now. will install itself into /$objtype/bin/aux/realemu
and install realemu (8) manpage.
impovement on the manpage is welcome as my english is not so good :)
aux/vga doesnt need to be changed for realemu. the thing that needs
change is the kernel vgavesa driver to use the file /dev/realmode
instead file instead of calling realmode() directly. this works with both, realemu
and the original #P/realmode file. so it does not break anything.
the patch:
/n/sources/patch/vesa-softscreen-resize
also fixes some some softscreen related mode switching bugs in devvga.c and
screen.c that are unrelated to realemu. (it would crash with #P/realmode too)
i forgot to submit the patch to allow writing the vga framebuffer
(0xA0000-0xBFFFF) with #P/realmodemem:
/n/sources/patch/realmodemem-vgamem
this makes switch switch back to textmode work properly in realemu.
/n/sources/patch/vesa-depth32
still, aux/vga does the channel string generation wrong for 32 bit depth
modes on vesa, but this is a separate patch and has no connection to realemu.
/n/sources/patch/devdraw-initscreenimage-from-isr
fixes kernel panic.
--
cinap
[-- Attachment #2: Type: message/rfc822, Size: 3361 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@9fans.net
Subject: Re: [9fans] realemu update
Date: Sun, 6 Mar 2011 09:35:00 +0200
Message-ID: <a3c9b4d5c5119c1f3a4a8d9debb28b08@proxima.alt.za>
> for everyone running realemu, please try with the new version to
> see if i broke something.
Why TARG=qi in the mkfile (I would have guessed 8i, but I could be
wrong)? and I think the error:
term% mk install
cp 8.out $BIN/qi
rc: null list in concatenation
mk: cp 8.out $BIN/qi : exit status=rc 9367: error
comes from not defining BIN?
Also, there's
usgae: ./8.out [-Dpt] [-s srvname] [-m mountpoint]
;-) but I'll gladly submit a man page if you throw a couple of
guidelines in my direction.
That said, I haven't tried it yet. I'm a little concerned about
aux/vga being altered to expect the emulation in /dev/realmode* and
what it may do if it's not there, which probably merely shows how
limited my understanding is.
I would like to see this type of change find its way into the
distribution permanently, I'll certainly help if I can.
++L
next prev parent reply other threads:[~2011-03-06 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 6:49 cinap_lenrek
2011-03-06 7:35 ` Lucio De Re
2011-03-06 18:48 ` cinap_lenrek [this message]
2011-03-07 4:21 ` Lucio De Re
2011-03-07 10:39 ` cinap_lenrek
2011-03-07 11:07 ` Lucio De Re
2011-03-07 11:50 ` cinap_lenrek
2011-03-07 12:23 ` erik quanstrom
2011-03-07 12:39 ` Lucio De Re
2011-03-07 14:19 ` Russ Cox
2011-03-07 14:44 ` Lucio De Re
2011-03-07 15:03 ` Russ Cox
2011-03-08 10:45 ` Stanley Lieber
2011-03-08 11:10 ` Stanley Lieber
2011-03-08 7:42 ` cinap_lenrek at gmx.de
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=08d2ecf0b69e5840218c2803692a5a5a@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).