Re: Geode driver question

I think that I found the problem.  The minimun clock frequency in line 844
of geode_driver.c is too high to allow the lower resolutions to be accepted:

static ClockRange GeodeClockRange = { NULL, 25175, 135000, 0, FALSE, TRUE,
1, 1, 0 };

Changing the minimum clock frequency to 1 solves the problem:

static ClockRange GeodeClockRange = { NULL, 1, 135000, 0, FALSE, TRUE, 1, 1,
0 };

Clearly, this is not a valid lower boundery, but it solves the problem, and
it looks like other drivers are taking the same approach of setting a
minimum of 0 or 1.

Also, the HorizSync range in XF86Config will need to allow a lower minimum
value so something like 10-60 will be necessary.

Hope this helps others,

Ed


----- Original Message -----
From: "Ed Anuff" <[email protected]>
To: <[email protected]>
Sent: Sunday, December 08, 2002 10:47 PM
Subject: Geode driver question


> I see from looking at the source that the new Geode driver supports
several
> modes such as 320x240 and 512x384 that I would like to make use of.
> Unfortunately, I've been unable to create a modeline that works with them.
> Does anyone have the set of modelines that match the resolutions supported
> by the new driver?
>
> Thanks
>
> Ed
>