9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Carmack johnc@idnewt.idsoftware.com
Subject: Quake on plan 9
Date: Wed,  2 Aug 1995 22:30:29 -0400	[thread overview]
Message-ID: <19950803023029.Z8vcDcSGafQaW4njswMuXlKF5KGg3umMEDyQxczWbTg@z> (raw)

I am going to buy a system to run plan 9 on.  Are there any =
integrators in the audience that will provide a ready-to-run, high =
performance pc system?  I want to be able to make a standalone =
plan 9 network with a pc and a couple old NEXTStations, as well as =
mount some NFS volumes from our main file server.

My first project will be to bring up Quake.  If anyone has any =
comments on troubles I am likely to run into, please let me know.  =
The game's requirements are:

Good keyboard event handling.  Up / down notifications for all =
keys is ideal, but I can live with some keys being special.

A rapid bitmap blitter.   Mapping the framebuffer is ideal.  A =
single copy to screen from shared memory is usually fine.  Pumping =
a bitmap through a generic imaging function generally isn't.  For =
actually playing games, as opposed to developing them, an easy way =
to change the display resolution, like xfree86, is great.

Low level sound access.  Mapping the recirculating dma buffers =
with a call to get the current dma position is ideal.  A blocking  =
write to a sound stream is fine if I can get tight control of the =
buffering done in the driver.  Does a sound driver even exist?  It =
sounds like a fun and straightforward project if not.

Non blocking, non buffering TCP/IP.  Any implementation that =
handles the BSD sockopts should be fine.

A way to get raw mickey counts from the mouse would be cool.  Our =
NEXTSTEP and X versions have to live without mouse input.

John Carmack
Id Software






             reply	other threads:[~1995-08-03  2:30 UTC|newest]

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

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=19950803023029.Z8vcDcSGafQaW4njswMuXlKF5KGg3umMEDyQxczWbTg@z \
    --to=9fans@9fans.net \
    /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).