9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rob@plan9.att.com rob@plan9.att.com
Subject: Quake on plan 9
Date: Thu,  3 Aug 1995 00:38:16 -0400	[thread overview]
Message-ID: <19950803043816.gSUkPf2U9loyp8_txeevlq9mcVxYGiR8R3n2HjzbXEQ@z> (raw)

You'll need to do some minor system hacking to give you up/down
events on the keyboard.  Plan 9 hides all that stuff for you as a service
to most software, so on machines that have up/down events (the
first few machines we ported to didn't) we generate UTF directly.
It would be a few minutes' work to make another device file that
gives you the up/down stuff in any form that's helpful.  Similar
comments apply to the mouse.  With a little more work, this could
even be made to work through the window system.

The framebuffer is mappable already, although you may need to
add a line to a table in the kernel and recompile before you can
get to it.  If you're on a VGA, you may also need a hook to get to
the routine that copies from the internal buffer to the page-mapped
display.  This is easy, too, although getting it to cooperate with the
window system is not.  (It's very easy in Brazil, but that's another
story.)

There is a sound driver for the Sound-Blaster cards and Nextstations.
I don't know it well enough to say if it does enough, but as you say
it's a straightforward project if not.

Again, unbuffered TCP/IP will take a little kernel work but not much.

-rob






             reply	other threads:[~1995-08-03  4:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-03  4:38 rob [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-08-04  9:21 Heiko
1995-08-03 21:42 rob
1995-08-03 20:14 Scott
1995-08-03  4:27 Gary
1995-08-03  3:04 philw
1995-08-03  3:04 philw
1995-08-03  2:30 John

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=19950803043816.gSUkPf2U9loyp8_txeevlq9mcVxYGiR8R3n2HjzbXEQ@z \
    --to=rob@plan9.att.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).