http://bugs.xfree86.org/show_bug.cgi?id=314
------- Additional Comments From [EMAIL PROTECTED] 2003-23-07 07:29 ------- Consider for example an unpatched X server with a patched DRM (only one of eight scenarios to consider): the DRI will be enabled, but the DRM will read the new fb_base field, which the X server has never initialized. Oops. Not to mention that it will read garbage for lots of fields, as the order of the fields in the struct has changed... an elegant solution might be to set the framebuffer aperture base using a new ioctl, which would implicitly tell the DRM to use the new memory layout. The clients could use another (or even the same?) ioctl to tell the DRM what they think the framebuffer aperture base is, so the DRM can fixup the client commands. The x11perf results show that accelerated image writes do pay off for non-GXcopy ROPs, I'll disable them for GXcopy. Thanks for testing. CP stands for Command Processor, the Radeon DMA command engine, which is used for issuing commands to the chip when the DRI is enabled. -- Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
