On Mon, 2005-01-24 at 14:24 +0100, Jerome Glisse wrote: > On Sun, 23 Jan 2005 15:54:26 -0500, Michel DÃnzer <[EMAIL PROTECTED]> wrote: > > On Sun, 2005-01-23 at 12:31 +0100, Jerome Glisse wrote: > > > > > > I was wondering what was the differences between using hostdata_blt > > > & bitblt_multi. One faster than other ? Do not use same path for reading > > > data ? > > > > Indeed, the BITBLT_MULTI type 3 packet only allows blits within the > > GPU's address space, whereas hostdata blits transfer data from the CPU > > (the host) to the GPU. The fact that the former works correctly just > > means that the source data in the framebuffer already has the correct > > byte order. > > BITBLT_MULTI work if i put data in the agpgart space with cpu (memcpy) > and then read it and put it in the framebuffer with bitblt_multi.
This still requires that the data is copied to AGP space with the correct byte order. This might indeed work for the 3D driver (Mesa can provide little endian texture data), but not as is in the X server. > > > RADEON_DP_GUI_MASTER_CNTL_C (0x1c84) > > > > Are you sure this is correct? At least on R200, 0x1c84 is a completely > > different register... > > I may have made an error copying the value :) at least i see > a RADEON_DP_GUI_MASTER_CNTL_C in radeon_reg.h in X server. It's unused though AFAICT, I can only assume it's an error. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
