On 2002.05.01 16:18 Leif Delgass wrote: > .... One thing I realized concerning blits: > the utah driver uses the host_data[0-15] registers to do blits which > treats blits as a GUI-master operation. This means it works with > pseudo-DMA. I think the better way to do it is to use the system bus > master method and interrupt handling that Frank has set up. However, if > we want to keep an MMIO mode, we'll have to have an alternate method for > blits.
I suppose we can do as we have been doing so far: using the MMIO frame buffer. Anyway, the MMIO support is interesting as a debugging aid, since theoretically every hardware should work with DMA. > > So before we starting the merge, it's needed to include the state > > update in the buffers. ... > > This would make the driver work more like the utah setup, so it might > make > it easier to reuse some of the code, and it would be easier to get the > proper order of state and vertex data in the buffers. Yes. I think that the gamma driver does this as well. > On the security > issue, I think we need to be careful about how we handle blits. Frank's > code for _dma_buffers allows sending buffers to the DRM, does that mean > this takes the place of _dma_vertex? I assume you still need to call > this to allocate the buffers before filling them. > The gamma driver also uses a general buffer submission DMA IOCTL instead of _dma_vertex, but I think that we could just use the current _dma_vertex interface for the time being, since they are semantically identical. José Fonseca
