Hi,

It looks like the radeon kernel command checker blocks some of
gl(x)info's 32 bit commands. Here's dmesg output

ioctl32(glxinfo:5153): Unknown cmd fd(4) cmd(80046402){t:'d';sz:4} 
arg(ff9b517c) on /dev/dri/card0
ioctl32(glinfo:5184): Unknown cmd fd(4) cmd(80046402){t:'d';sz:4} arg(ff86c5dc) 
on /dev/dri/card0
ioctl32(glxinfo:9875): Unknown cmd fd(4) cmd(80046402){t:'d';sz:4} 
arg(ffed0e1c) on /dev/dri/card0

The result is that glinfo & glxinfo reports bogus data with KMS enabled:
$ glinfo|egrep 'RENDER|VENDOR'
GL_RENDERER: Software Rasterizer
GL_VENDOR: Mesa Project

... whereas openarena does show the proper strings and (more
importantly) run smoothly using hw acceleration.

This is with 32bit glinfo on 64bit kernel (2.6.31 final with
CONFIG_DRM_RADEON_KMS=y, libdrm). Both 32b & 64b build of libdrm-2.4.13
have been build --enable-radeon-experimental-api. In fact all are
standard packages from Mandriva Cooker.

Note that the 64bit build works nicely:

# ./32/glinfo |egrep 'RENDER|VENDOR'
GL_RENDERER: Software Rasterizer
GL_VENDOR: Mesa Project
# ./64/glinfo |egrep 'RENDER|VENDOR'
GL_RENDERER: Mesa DRI R300 (RV350 4150) 20090101  TCL DRI2
GL_VENDOR: DRI R300 Project

Maybe a compat ioctl issue?

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to