Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-08-20 Thread Branden Robinson
On Fri, Aug 20, 2004 at 05:48:10AM -0700, Mike Mestnik wrote: > Your getting on the right page. However the manpage should also indicate > that any suffix for dotclock will result in an "echo (EE) $msg; exit;". > This is preventing me from knowing what the unit is, since it can't be > changed. U

Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-08-20 Thread Mike Mestnik
Your getting on the right page. However the manpage should also indicate that any suffix for dotclock will result in an "echo (EE) $msg; exit;". This is preventing me from knowing what the unit is, since it can't be changed. --- Branden Robinson <[EMAIL PROTECTED]> wrote: > On Fri, Aug 13, 2004

Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-08-20 Thread Branden Robinson
On Fri, Aug 13, 2004 at 11:53:27AM -0700, Mike Mestnik wrote: > > 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. According to radeon(4x), > > specif

Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-08-13 Thread Mike Mestnik
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 >

Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-08-13 Thread Branden Robinson
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 rang

Processed: Re: Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-08-13 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 261620 + moreinfo Bug#261620: xserver-xfree86: [ati/radeon] radeon(4x) needs better documentation of ForceMinDotClock option Tags were: upstream Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. De

Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-07-27 Thread Michel Dänzer
On Mon, 2004-07-26 at 21:25 -0500, Mike Mestnik wrote: > > 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. T

Bug#261620: Radeon: ForceMinDotClock has no effect.

2004-07-26 Thread Mike Mestnik
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