From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <006201c02737$16df6e80$0301a8c0@freeze>
From: "Matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
References: <E13dfR9-000E2q-0Y@anchor-post-34.mail.demon.net>
Subject: Re: [9fans] any vga driver gurus about?
Date: Mon, 25 Sep 2000 22:25:07 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 0de21ed4-eac9-11e9-9e20-41e7f4b1d025

<snip> thanks

> Which chip is it that is not supported? I would have thought
> all the Cirrus CL-GD chips were supported.

it's a cl-gd7543

it's got an entry on vgadb which directs to the clgd542x.c driver

ctlr
    0xC0039="CL-GD7543"    # notebook
    link=vga
    ctlr=clgd542x
    hwgc=clgd542xhwgc

but from aux/vga I get a response of
clgd542x: unknown chip id - 0x30

looking in clgd542x.c I see that 0x30 is not part of the static :

static Gd542x family[] = {
          { 0x88,  75000000, },           /* CL-GD5420 */
          { 0x8C,  80000000, },           /* CL-GD5422 */
          { 0x94,  80000000, },           /* CL-GD5424 */
          { 0x90,  80000000, },           /* CL-GD5426 */
          { 0x98,  80000000, },           /* CL-GD5428 */
          { 0x9C,  86000000, },           /* CL-GD5429 */
          { 0xA0,  86000000, },           /* CL-GD5430 */
          { 0xA8, 90000000, },            /* CL-GD5434 */
          { 0xAC, 135000000, },           /* CL-GD5436 */
          { 0xB8, 135000000, },           /* CL-GD5446 */
          { 0x00, },
  };

which makes identify() barf.

Looking through the cl-gd7543 manual the stuff is mostly the same
I think the general difference is that it has ntsc/pal output

I was hoping that just putting an entry in the Gd542x family[] would work.

Matt