9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VGA and laptops
Date: Tue, 26 Sep 2000 21:48:21 +0100	[thread overview]
Message-ID: <E13e1eO-000PRr-0K@tele-post-20.mail.demon.net> (raw)

> I do have a question though, wasn't VESA compliance supposed to do away with
> these problems

It does, if you feel like you can put your trust in someone's BIOS.... Making a call
into the BIOS is hairy in that you have no way to make it adhere to the particular
set of rules which your operating system makes on drivers, e.g. time spent with
interrupts off, how long spent spinning waiting for VBE etc..

As a result, one can imagine using it as a means to get the right screen mode at
the start, but you would never think of making calls to it for accelerated drawing.
So you can get a frame buffer and then bit bash, which I accept is a whole lot
better than nothing.

However, if you want an accelerated driver, then there are typically interrelationships
between the screen mode, and the blitter, so VESA is not much help. Putting it
another way, to be able to accelerate a chipset, you would probably need
to understand every setting that VESA makes; if so, then why use it?

VNH's native Inferno uses VESA calls to initialise the screen mode.




             reply	other threads:[~2000-09-26 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-26 20:48 nigel [this message]
2000-09-26 20:50 ` [9fans] that plan 9 creature/icon thing Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2000-09-27  0:37 [9fans] VGA and laptops jmk
2000-09-26 18:33 nigel
2000-09-26 18:49 ` Matt
2000-09-26 13:25 jmk
2000-09-26 16:37 ` Latchesar Ionkov
2000-09-26 18:05   ` Matt
2000-09-26 13:23 jmk
2000-09-26 20:29 ` Christopher Nielsen
2000-09-28 11:21 ` Latchesar Ionkov
2000-09-29  4:01   ` rob pike
2000-09-29 16:50     ` Latchesar Ionkov
2000-09-26  9:13 saroj
2000-09-26 13:29 ` Latchesar Ionkov
2000-09-27 10:52 ` Axel Belinfante

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=E13e1eO-000PRr-0K@tele-post-20.mail.demon.net \
    --to=nigel@9fs.org \
    --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).