On Thu, 28 Feb 2002, Jos� Fonseca wrote:
> Leif,
>
> I've finished the work on the the mach64_* files except for the
> *_{tris,vb} ones. I've also included the remaining of your changes.
>
> There still are several things that I'm not sure, but I'll leave those
> issues to the moment that we are able to link the driver. At that time it
> will be necessary to make an exaustive review of all code to check if
> things are properlly made, otherwise debugging will be too painful.
>
> _vb.c is not so hardware specific so, although can give some extra work,
> it should be more or less straighforward to bring to date.
I've been working on this, starting from the r128 version. I've made
numerous changes to mach64_context.h (and elsewhere) to make this match up
better, and am trying to clean up the mach64_ioctl.[ch] to match up better
as well. This is where we can do some of the DMA work in advance, using
the r128 functions as a basis. For now, everything will be done in the
mach64UploadHwStateLocked. See below for more on this..
> On the other hand, in _tris.c the copy & paste approach is useless. I
> think the best here is start from scratch with the exported functions and
> build the rest upon that.
For _tris.c, my idea was to take some of the r128 code and add it in but
disable it. That way the DMA method will be there to work on, but for now
we'll have to duplicate the primitive functions to do the direct register
programming. I still have a ways to go on this yet. If I can get things
to a somewhat sane state, I'll pass along a diff.
> I don't know if you have any work done on this, otherwise I'll start
> hacking a little on both.
>
> Regards,
>
> Jos� Fonseca
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
--
Leif Delgass
http://www.retinalburn.net
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
