9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: George Michaelson <ggm@dstc.edu.au>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hardware acceleration
Date: Wed, 14 Feb 2001 11:08:02 +1000	[thread overview]
Message-ID: <20550.982112882@dstc.edu.au> (raw)
In-Reply-To: Your message of "Tue, 13 Feb 2001 19:45:01 EST." <20010214004507.48578199D5@mail.cse.psu.edu>


The relative importance of something like VESA isn't running it
permanently: its being able to use it to bootstrap.

Nigel offered to help me get a G400 working. I couldn't get his
mods into a floppy, and get it to work, not the least because the
boot/install floppy is already near max size, and because frankly,
the install process is baroque.

If I'd been able to use a VESA mode driver to get to a running state
however slow, slipping his mods in would have been trivial.

As a put-off to newbies, install is a big one. And if you discount
flamage about the relative merits of Paris to Pennsylvania a really
large number of Qs in the mail seem to be about making p9 work on
hardware that is both modern, easy to buy, and demonstrably working
(albiet from arcane and crude codehacks) for other s/w systems.

I do sympathise with people who have to cut this code saying that
its not a 100% solution, but the current one is way below 80:20 and
could (I suspect) with VESA be a lot closer.

If you look at the circumstances of a P9 newbie, its increasingly
unlikely they will have the hardware specs in the install page. So
this problem only gets worse.

How about writing it to drive off the serial port, and bypassing the
screen altogether for some level of bootstrap?

-George



  reply	other threads:[~2001-02-14  1:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14  0:45 Russ Cox
2001-02-14  1:08 ` George Michaelson [this message]
2001-02-14  1:40 Russ Cox
2001-02-14  1:56 ` George Michaelson
2001-02-14  9:41   ` Douglas A. Gwyn
2001-02-14  2:28 Russ Cox
2001-02-14  7:01 Russ Cox
2001-02-14  7:44 nigel
2001-02-14 10:24 forsyth
2001-02-14 12:42 William Staniewicz

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=20550.982112882@dstc.edu.au \
    --to=ggm@dstc.edu.au \
    --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).