On Wed, Oct 17, 2001 at 11:45:39AM +0000, [EMAIL PROTECTED] wrote: > Thank you very much. I'll try to see what is missing in the GUI DMA test > in the DRI code. > At a first glance, I don't remember to have seen a pci_set_master call > anywhere in the DRI code. It seems important, doesn't it?
That enables bus master in the pci config registers, IIRC. Simplest test case, one descriptor: Set Frame buffer offset to 0. Set System buffer offset to 0. Set BM_COMMAND to 4096 | 1 << 31 (End of descriptor list). Set BM_Reserved to 0. Write bus address of buffer to BM_SYSTEM_TABLE | SYSTEM_TO_FRAME_BUFFER (which happens to be 0.) If the top line or two of your display (depends on res/depth) are corrupted, then it works. Don't forget to change the PCI_ID or the module most likely won't load. The module was written for 2.4; It shouldn't need much to backport. It does assume x86-sized ints and probably other no-nos. There are several constants I should replace with #defines, as well. I was just happy to get it working reliably on my machine. Triggering module is simple; run a dd if=/dev/atidma of=test.raw bs=307200 count=1. atidma is character device major 240 minor 0. > > > > > > Have not tried GUI dma, but it is quite similar. > Easier indeed. The directives in the Mach64 Programmer's manual are simpler > than for the case you're working on. > > I'm now at work but impacient to get home and have access to the Mach64 DRI > code. > > Thanks again. No problem :) Been itching to get this working for a long time. R C -- They said it was *daft* to build a space station in a swamp, but I showed them! It sank unto the swamp. So I built a second space station. That sank into the swamp too. My third space station sank into the swamp. So I built a fourth one. That fell into a time warp and _then_ sank into the swamp. But the fifth one... stayed up! --Monty Python/Babylon 5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
