9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] termrc and aux/realemu
Date: Sun, 17 Aug 2014 03:54:01 +0200	[thread overview]
Message-ID: <a2ae46c8b25164840d6c4efa99b851b7@felloff.net> (raw)
In-Reply-To: <6e9db28ce5e4bac6fac9fa0c0c463e7b@saturn.jitaku.localdomain>

every video mode is special. aux/vga does special stuff for
every one of them like mapping mmio registers from named
hardware segments or reading/writing special control files
of the kernel half driver. vesa works with doing vesa bios
calls. /dev/realmode was initially provided by the kernel,
by doing a mode switch to realmode and executing the code.

with realemu /dev/realmode is provided by userspace fileserver
which binds over /dev and hides the kernel mode /dev/realmode
files.

these days, 9front has no kernel mode /dev/realmode anymore
as realemu works good enougth and realmode isnt even available
in 64 bit kernel. the modularity remains. this is good for
debugging, as you can run realemu with tracing modes
that let you see what io ports are read and written by
the video bios code. also, mounting and unmounting lets
us make snapshots of the bios memory areas to rerun tests
from a defined state the video bios memory. (theres the
vbt program and scripts to try to bruteforce hidden video
modes that uses this).

conflating aux/vga with realemu isnt right in my opinion.
realemu can be used in many different ways and is not limited
to running vesa bios code (see comload) and aux/vga has no
need to depend on it directly.

--
cinap


  reply	other threads:[~2014-08-17  1:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-16  5:55 sl
2014-08-16 23:42 ` kokamoto
2014-08-17  1:54   ` cinap_lenrek [this message]
2014-08-17  4:22     ` kokamoto
  -- strict thread matches above, loose matches on Subject: below --
2014-08-16  0:40 sl
2014-08-16  5:29 ` kokamoto
2014-08-14  1:40 kokamoto
2014-08-14  2:17 ` [9front] " Nick Owens
2014-08-15  0:10   ` kokamoto
2014-08-15  0:28     ` Nick Owens
2014-08-15  0:46     ` sl
2014-08-16  0:14       ` kokamoto
2014-08-16  0:17       ` kokamoto
2014-08-16  0:52         ` cinap_lenrek
2014-08-16  5:39           ` kokamoto

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=a2ae46c8b25164840d6c4efa99b851b7@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9front@9front.org \
    /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).