On 17 Dec 2002, Chris Worley wrote:
> I look at the register indices being used and I'm stumped... The X
> driver register offset is (mga_reg.h):
>
> #define MGA1064_GEN_CTL 0x1d
That matches both the Mystique (MGA1064) and the G200 docs I have.
>
> While the frambuffer driver uses an enum that would make
> "POS1064_XGENCTRL" an offset of 0x0f (in matroxfb_DAC1064.h):
>
> enum POS1064 {
> POS1064_XCURADDL=0, POS1064_XCURADDH, POS1064_XCURCTRL,
> POS1064_XCURCOL0RED, POS1064_XCURCOL0GREEN, POS1064_XCURCOL0BLUE,
> POS1064_XCURCOL1RED, POS1064_XCURCOL1GREEN, POS1064_XCURCOL1BLUE,
> POS1064_XCURCOL2RED, POS1064_XCURCOL2GREEN, POS1064_XCURCOL2BLUE,
> POS1064_XVREFCTRL, POS1064_XMULCTRL, POS1064_XPIXCLKCTRL,
>POS1064_XGENCTRL,...
> When I compare the other register offsets in these two files for this
> DAC register set, it still makes no sense; the offsets are close, but
> different and in different orders.
These are in the order of my docs., but they show spaces between some of
these registers; the frambuffer driver doesn't have a mapping array for
this list of interesting registers to their addresses does it ?
--
Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge
[EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
