Testing r100 with 2.6.32.2 kernel and F12 userspace

[chrisr]

KMS correctly initialises DVI-0 to its native 1280x1024 resolution. However, compiz fails to run:

[drm:r100_cs_track_texture_check] *ERROR* Texture of unit 0 needs 250880 bytes but is 4096
[drm:r100_cs_track_texture_print] *ERROR* pitch                      5120
[drm:r100_cs_track_texture_print] *ERROR* use_pitch                  1
[drm:r100_cs_track_texture_print] *ERROR* width                      1280
[drm:r100_cs_track_texture_print] *ERROR* width_11                   2048
[drm:r100_cs_track_texture_print] *ERROR* height                     49
[drm:r100_cs_track_texture_print] *ERROR* height_11                  2048
[drm:r100_cs_track_texture_print] *ERROR* num levels                 0
[drm:r100_cs_track_texture_print] *ERROR* depth                      0
[drm:r100_cs_track_texture_print] *ERROR* bpp                        4
[drm:r100_cs_track_texture_print] *ERROR* coordinate type            0
[drm:r100_cs_track_texture_print] *ERROR* width round to power of 2  0
[drm:r100_cs_track_texture_print] *ERROR* height round to power of 2 0
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

Textured video seems to work OK, but xine-ui's on-screen display still stops the X server from responding. Basically, the dmesg log fills up with messages like:

[drm:r100_cs_packet_parse] *ERROR* Packet (0:0:99) end after CS buffer (34) !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:r100_cs_packet_parse] *ERROR* Packet (0:0:99) end after CS buffer (90) !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[drm:r100_cs_packet_parse] *ERROR* Packet (0:0:99) end after CS buffer (34) !
[drm:radeon_cs_ioctl] *ERROR* Invalid command stream !

and you become unable to click on anything any more, although you can still move the mouse pointer. Switching to a console and SIGHUPing the Xorg process restores control.

[agd5f]

3D on r1xx and r2xx may have regressed in some cases since the transition to KMS support as fewer people test the older hardware. If you are seeing regressions please report bugs:

https://bugs.freedesktop.org

Apart from that, 3D support on r1xx and r2xx is pretty much stable and feature complete.