From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b541b3f95e5e2d8224751e86f52cf6d2@plan9.bell-labs.com>
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Yet another VGA issue (CT65550)
In-Reply-To: <20030506015936.GF5035@swordfish>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon,  5 May 2003 22:11:44 -0400
Topicbox-Message-UUID: 9ec6f454-eacb-11e9-9e20-41e7f4b1d025

Since there's no PCI info, I'm guessing the CT65550 (if it is such)
is connected via a Vesa Local Bus (VLB). 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.