From: rog@vitanuova.com
To: knapjack@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] VBE 1.2/2.0+ functions for Plan9
Date: Tue, 30 Nov 2004 12:51:07 +0000 [thread overview]
Message-ID: <06363cbeb3585bb77c6304de31b0478b@vitanuova.com> (raw)
In-Reply-To: <6e35c062041129122170cedf5e@mail.gmail.com>
> I thought earlier grumbles about VESA support were about hardware vs.
> software cursors and some related gymnastics?
yes, i'd forgotten about this.
when i did the VESA support for inferno, it had software cursor support.
it might be quite a pain to put it back into plan 9.
next prev parent reply other threads:[~2004-11-30 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 16:44 Devon H. O'Dell
2004-11-25 17:13 ` rog
2004-11-25 18:57 ` Devon H. O'Dell
2004-11-29 20:21 ` Jack Johnson
2004-11-30 12:51 ` rog [this message]
2004-11-30 10:40 ` Devon H. O'Dell
2004-11-30 11:08 ` Tiit Lankots
2004-11-30 11:21 ` Devon H. O'Dell
2004-11-30 11:28 ` Tiit Lankots
2004-11-30 11:37 ` Devon H. O'Dell
2004-11-26 3:03 Fwd: " Bob Hartley
2004-11-26 3:04 ` boyd, rounin
2004-11-26 3:08 ` Russ Cox
2004-11-26 4:19 ` Bob Hartley
2004-11-26 5:52 ` Devon H. O'Dell
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=06363cbeb3585bb77c6304de31b0478b@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
--cc=knapjack@gmail.com \
/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).