El Sáb 22 Sep 2001 14:54, escribiste:
> Hi guys!
>
> I've had lot of other things to do in the past weeks so I couldn't work
> on mach64. I've still problems to compile the trunk with Manuel's
> patches. I haven't had time to track this down, so I decided to post my
> changes of mach64_dma.c which I have made in my copy of the
> mach64-branch.
Perhaps the problem is that you're using a different trunk (as somebody said
some time ago).
>
> It is possible, that the mach64_dma.c doesn't compile because I couldn't
> test it. If something fails please report to me; there may be cut and
> paste errors.
I've just replacing my mach64_dma.c with yours, and it compiles fine. Sadly,
I'm getting the same results than before changing it.
I've seen that you're using the same setup than the code I had changed. So,
you're using:
bus_cntl = (( MACH64_READ( MACH64_BUS_CNTL ) | 0x08000000 ) &
~MACH64_BUS_MASTER_DIS) & ~0x10;
and I'm using:
MACH64_WRITE( MACH64_BUS_CNTL, MACH64_READ( MACH64_BUS_CNTL) |
MACH64_BUS_EXT_REG_EN );
MACH64_WRITE( MACH64_BUS_CNTL, MACH64_READ( MACH64_BUS_CNTL ) &
~MACH64_BUS_APER_REG_DIS );
I had the hope to find any difference, but it's just the same, because
MACH64_BUS_EXT_REG_EN=1<<27 (0x08000000)
and
MACH64_BUS_APER_REG_DIS=1<<4 (0x10)
So, I'll make some changes to my code to use your reset procedure and your
memory allocation (it must be better than mine, because no procedure could be
more dirty than the one I wrote ).
The next thing I will try is putting the dma test code in a separate
function, to test if it works in the dma_cleanout as Frank notified.
>
> --Andreas Karrenbauer
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
