On Fri, 7 Nov 2003, Mark Vojkovich wrote:
Everywhere
in the driver hex values are given premultiplied by 4 it seems,
and specified as VALUE/4.
The register pointers are dword pointers. The register offsets
are byte offsets. They are written as VALUE/4 so that I can grep
for VALUE.
Mike A. Harris wrote:
On Fri, 7 Nov 2003, Mark Vojkovich wrote:
Everywhere
in the driver hex values are given premultiplied by 4 it seems,
and specified as VALUE/4.
The register pointers are dword pointers. The register offsets
are byte offsets. They are written as VALUE/4 so
On Sun, 9 Nov 2003, Kevin Brosius wrote:
Well, gee, Mike... You're question was filled with negative
assumptions about why the driver might be 'obfuscated'. You
shouldn't take offense if Mark is a little short with you.
Focus on asking a question, leaving off the insinuations, and
you'll get
[size problem solved over private e-mail; it was due to using X-TT,
which links against all of its ``encoding converters''; Jessi's X
server is now 866KB, which is still a wee bit over what I'd expect.]
JB can anyone plz tell me what devices does Xfbdev(and Xipaq)
JB expect in the /dev/
Mike A. Harris wrote:
I suppose that is fair enough. I'm trying to debug an annoying
problem in the driver for some users having problems, and seeing
hexadecimal registers everywhere instead of symbolic names is
very frustrating.
Mike, I really can't imagine how symbolic names would help you
On Sun, 9 Nov 2003, Thomas Winischhofer wrote:
I suppose that is fair enough. I'm trying to debug an annoying
problem in the driver for some users having problems, and seeing
hexadecimal registers everywhere instead of symbolic names is
very frustrating.
Mike, I really can't imagine how
On Sun, Nov 09, 2003 at 05:24:02PM +0100, Juliusz Chroboczek wrote:
[size problem solved over private e-mail; it was due to using X-TT,
which links against all of its ``encoding converters''; Jessi's X
Hmm, that should only happen if XTTInLibXFont is turned on.
server is now 866KB, which is
I agree that with hex values the driver is much harder to read and
debug (as a casual developer). that's part of the reason the radeon
driver is so well developed and feature-rich. however, I'd say that
most drivers in xfree86 use hex values rather than symbolic names so
symbolic names are
