Bug#261620: Radeon: ForceMinDotClock has no effect.
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@example.com> wrote:
> tag 261620 + moreinfo
> 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
> > 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
> You confused me in that message. You said you had to add "M" to the
> value to get XFree86 to interpret the value as being in *hertz*?
> That seems pretty counter-intuitive to me. According to radeon(4x),
> specifying "M" would mean "megahertz".
> G. Branden Robinson | The Rehnquist Court has never
> Debian GNU/Linux | encountered a criminal statute
> firstname.lastname@example.org | did not like.
> http://people.debian.org/~branden/ | -- John Dean
> ATTACHMENT part 2 application/pgp-signature name=signature.asc
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!