XPost: linux.debian.maint.x
From:
[email protected]
That's right in *hertz* to mean "megahertz". I.E DotClock 21.96 VS
DotClock 21.96M, for all I know it's DotClock 21.96K!! That's what I'm
saying that it's not documented what 21.96, from my mode section, means.
--- Branden Robinson <
[email protected]> wrote:
tag 261620 + moreinfo
thanks
On Mon, Jul 26, 2004 at 09:25:41PM -0500, Mike Mestnik wrote:
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-6
Severity: wishlist
Option "ForceMinDotClock" "9M"
(**) RADEON(0): Option "ForceMinDotClock" "9M"
(II) RADEON(0): Clock range: 20.00 to 350.00 MHz
As you can see from my cfg file, I'm trying to use a doublescan mode 256x240. This is the native resolution of an NES pumped up a bit.
It's an asumption of mine that DotClock is in Mhz, that is missing
from
XF86Config-4's man page.
I can't reply to your response to Michel D�nzer, as you sent that to the bug's -quiet address (in fact, I didn't even see that response until
just
now).
You confused me in that message. You said you had to add "M" to the
option
value to get XFree86 to interpret the value as being in *hertz*?
That seems pretty counter-intuitive to me. A