9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Consindering eBox-4854 for Plan9
Date: Fri, 15 Feb 2008 13:56:21 -0500	[thread overview]
Message-ID: <12c0010c5469c352163ca26926f593ee@quanstro.net> (raw)
In-Reply-To: <13426df10802151051w531f272ej9e98f773ce34df0d@mail.gmail.com>

>>  actually programming documentation or just code?
> 
> just code, but, while I realize code alone is often useless, I am
> willing to bet the docs in this case are less useful than code. The
> code will have all the huge doc gaps filled in.

☺.  it seems to be a truism among hardware folks.  the worse
the documentation is, the more tightly it is kept.

the via parts do a very good job with vesa.  i find our 800mhz
terminals very usable.  the graphics are pretty snappy.

i think it would be more of a priority to tackle the amd(ati)
and intel parts for which there is actual documentation.
intel documentation is not that great, but, you can learn
to live with it.

fortunately adding one more thing to the list of things
to do will not decrease the amount of my infinite spare
time.

- erik


  reply	other threads:[~2008-02-15 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15  9:51 TheAbysmal
2008-02-15 12:38 ` erik quanstrom
2008-02-15 18:39   ` ron minnich
2008-02-15 18:47     ` erik quanstrom
2008-02-15 18:51       ` ron minnich
2008-02-15 18:56         ` erik quanstrom [this message]
2008-02-15 19:01           ` ron minnich
2008-02-15 19:16             ` erik quanstrom
2008-02-15 21:09 ` John Barham
2008-02-15 21:16   ` John Barham

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=12c0010c5469c352163ca26926f593ee@quanstro.net \
    --to=quanstro@quanstro.net \
    --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).