On Sun, 2002-07-21 at 10:56, James Ralston wrote:
> On 17 Jul 2002, Michel Dänzer wrote:
>
> > On Wed, 2002-07-17 at 08:58, James Ralston wrote:
> >
> > > (I'd be willing to take a crack at writing a man page for the
> > > radeon driver,
> >
> > Great! That's very much appreciated.
>
> Attached is the first draft.
>
> Besides general proofreading and review, there are 16 FIXMEs in the
> first draft; I would appreciate help in clarifying the points they
> raise.
>
> > While you're at it, please also add the documentation for options to
> > programs/Xserver/hw/xfree86/Options, which can be used by
> > configuration tools like xf86cfg.
>
> I'll do that once I have something approaching a final version for the
> radeon(4x) man page (to minimize the number of edits I'll have to do
> in two places).
Good.
Comments (mostly looking at the FIXMEs :):
- reports are probably best directed to this list
- I'd rephrase the description of Option "UseFBDev" along the lines of:
Option "UseFBDev" "boolean"
If set to true, XFree86 will attempt to use use an
OS-specific framebuffer device interface. See
fbdevhw(4x) for further information. XFree86 will fail
to start up if this doesn't work.
The default is false (meaning, an OS-specific
framebuffer device interface will not be used,
the chip will be programmed directly).
Don't miss the 'device' after 'framebuffer'. :)
- the video key is a special color value which is replaced by the video
overlay if and where it's active. It only needs to be changed if the
default value causes undesired effects.
- I think it's correct that the multihead options have no effect with
cards without multiple ports (assuming that all cards with multihead
capable chips have multiple ports)
- I think the comment in RADEONPreInitModes() is accurate, the one in
RADEONGetBIOSParameters() is probably outdated
- the DRI options (except the AGP options) are mostly for debugging and
shouldn't normally be needed. I think describing them might cause more
confusion than it helps. FWIW the r128 manpage doesn't document them.
- yes, Option "AGPMode" does override the AGP mode. I think the
speed-stability tradeoff is well described.
- I don't think Option "AGPSize" is related to the AGP aperture size. It
determines how much of it the driver actually uses, so I'd expect it to
be limited by the aperture size. Again, this shouldn't need to be
changed, certainly not until the driver supports AGP texturing.
Hope this helps, keep up the good work
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
