[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#261620: Radeon: ForceMinDotClock has no effect.

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),
> > specifying "M" would mean "megahertz".
> 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.

You are still confusing me.

Are you simply saying that the manpage should document what units are used
if no suffix at all is provided?

G. Branden Robinson                |    I must confess to being surprised
Debian GNU/Linux                   |    by the magnitude of incompatibility
branden@debian.org                 |    with such a minor version bump.
http://people.debian.org/~branden/ |    -- Manoj Srivastava

Attachment: signature.asc
Description: Digital signature

Reply to: