From: Matt Gushee <mgushee@havenrock.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Yet another VGA issue (CT65550)
Date: Mon, 5 May 2003 20:42:27 -0600 [thread overview]
Message-ID: <20030506024227.GG5035@swordfish> (raw)
In-Reply-To: <b541b3f95e5e2d8224751e86f52cf6d2@plan9.bell-labs.com>
On Mon, May 05, 2003 at 10:11:44PM -0400, jmk@plan9.bell-labs.com wrote:
> Since there's no PCI info, I'm guessing the CT65550 (if it is such)
> is connected via a Vesa Local Bus (VLB).
Yes, that's what the specs say.
> The aux/vga code doesn't handle
> that, neither does the kernel part of the driver. Code needs to be
> added to recognise the chip revision and to set up the framebuffer
> in an unallocated memory range, etc. It's probably not hard, but awkward
> without the machine to hand.
:-((
Maybe I should finally learn C, so I can do it.
Oh well, I guess that machine's going back to Linux. I'm not
discouraged, but I want at least a windowing system and a usable text
editor on that box by tomorrow, so ...
I'll be back someday, as time allows. Thanks to you and 'rsc' for the
prompt attention.
--
Matt Gushee When a nation follows the Way,
Englewood, Colorado, USA Horses bear manure through
mgushee@havenrock.com its fields;
http://www.havenrock.com/ When a nation ignores the Way,
Horses bear soldiers through
its streets.
--Lao Tzu (Peter Merel, trans.)
next prev parent reply other threads:[~2003-05-06 2:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 20:08 Matt Gushee
2003-05-05 20:24 ` rsc
2003-05-05 21:55 ` Matt Gushee
2003-05-05 22:01 ` rsc
2003-05-06 1:59 ` Matt Gushee
2003-05-06 2:11 ` jmk
2003-05-06 2:42 ` Matt Gushee [this message]
2003-05-06 6:57 ` Jim Choate
2003-05-06 7:15 ` M.Stein
2003-05-06 6:46 ` [9fans] " Jim Choate
2003-05-06 7:47 ` Charles Forsyth
2003-05-06 9:42 ` Charles Forsyth
2003-05-06 11:42 ` [9fans] Cross-Building (was: Yet another VGA issue (CT65550)) Jim Choate
2003-05-06 14:36 ` [9fans] Yet another VGA issue (CT65550) splite
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=20030506024227.GG5035@swordfish \
--to=mgushee@havenrock.com \
--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).