9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 in VMware?
Date: Wed, 14 Feb 2001 12:49:03 +0000	[thread overview]
Message-ID: <20010214114414.E9120199D5@mail.cse.psu.edu> (raw)

forsyth wrote:
> >>As far as your other reservations, VESA defines a protected mode interface
> >>which requires only (from memory):
>
> true, but i believe roger found that many cards don't implement that.

to be more accurate, i didn't manage to find a single card that
implemented it, despite trying a fair old few.

the main portion of the VESA stuff i wrote was a load of 8086 code
(using those delicious cpp macros found in boot/pc/x16.h) to set up the
graphics mode, show a test card and query the user that it was ok.

it also filched the default font from the BIOS (hence no need for extra
font code in b.com) and passed info on the card (and framebuffer address,
etc) through to the main kernel.

for cards that didn't implement a linear frame buffer (a dying breed
now, i hope) i managed to find buffer switching code out there on the
net which did the job for many graphics cards.

i did rely on inferno's software mouse cursor though - how difficult
would it be to put one back into plan 9?

i do like the idea of simulating the BIOS code...  that approach could
get rid of a lot of the above dross.  it's kind of baroque though, an
entire x86 emulator just to get around a crappy software interface!

  cheers,
    rog.



             reply	other threads:[~2001-02-14 12:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 12:49 rog [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-13 22:24 forsyth
2001-02-13 19:56 Russ Cox
2001-02-13 21:28 ` Christian Smith
2001-02-13 21:34   ` Scott Schwartz
2001-02-05  9:56 Jim Niemira
2001-02-05 14:22 ` Ish Rattan
2001-02-13 14:20   ` Jim Niemira
2001-02-13 15:13     ` Christian Smith

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=20010214114414.E9120199D5@mail.cse.psu.edu \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /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).