如何编译内核模块使ati r600支持3D?

整个编译2.6.32rc1失败了，手动编译出radeon.ko, drm.ko复制过去又不行，mesa-git什么的都装了。

kernel 2.6.32还没有出来吧！

我是说rc版

如果没记错的话2.6.31就可以了。但是mesa需要高版本。不支持KMS

看官方论坛有人发了个howto帖子。

2.6.32会支持R600的KMS+3D

你又记错了，r600开3D需要的模块到2.6.32才会合并到内核，2.6.31不支持，必须另装模块：drm-radeon-module-git-r6xx-r7xx-3d。arch官方论坛的帖子说：

http://bbs.archlinux.org/viewtopic.php?id=79509

早在2.6.30的时候就看到更新支持R600

而且9月8日的时候airlied也说实现了R600的KMS+2D，3D

当然是否能够成功我并不能确定，没条件测试。BBS上需要agd5f的分支里面的模块，不知道是否必须。

确实，不装drm-radeon-module-git-r6xx-r7xx-3d没3D，也没KMS，但是现在agd5f的分支里已经没有drm模块了，只能编译2.6.32了

我编译2.6.32内核失败了，有什么办法只编译内核里的drm模块？

仁兄看新闻时真该仔细点。2.6.30是为R600提供了支持，但提供的是EXA和Xv加速，没有3D加速。再说R600/R700的3D加速4月中旬才启动，会立即并入六月发布的2.6.30里吗？

9月8日的phoronix有关Airlie的内容是：
http://www.phoronix.com/scan.php?pag...item&px=NzUxNg

9月9日的phoronix关于kernel的新闻是这么说的：
http://www.phoronix.com/scan.php?pag...item&px=NzUyMA

感谢提醒了，不可能都这么仔细的，只能走马观花的看看。。喜欢ls这样的认真劲

我编译了2.6.32rc1里的radeon.ko和drm.ko，为什么还是没有KMS和3D?

搭车问支持R700不？现在用的集成的N卡，想买独立显卡，目前A卡性价比好些。

r700好像没3D……

是一样的。只不过可能没KMS。不知道ls怎么单独编译两个模块的？我一直没找到方法。还是编译整个内核单独提取的？

make SUBDIRS=drivers/gpu/drm modules
不过后几次编译都失败了，不知为什么。

装上agd5f分支的modules了，怎么还是没3D？

重启，按照bbs上howto来。看看glxinfo，dmesg等信息

glxinfo |grep -i opengl
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.7-devel
OpenGL shading language version string: 1.20
OpenGL extensions:

你都编译了些什么东西。内核模块，libdrm，mesa，xf86-video-ati各自的git版本是否按顺序编译

内核模块，libdrm，mesa，xorg-server，xf86-video-ati xf86-input-evdev

编译的话，红色部分别忘了。

红的给忘了，也没按顺序编……

到底是x桌面的3D加速还是GLX的3D加速？这俩不是一个东西，一个是DDX，一个是DRI。
GLX的ATI硬件3D加速一般应该叫ati-dri之流的。

kwin不用的opengl吗

鬼知道用的啥，维基上只说是用的Qt。
都2009年了，X那套2D 3D API分离而且图形渲染还要经过进程通信的构架简直就是倒行逆施，最后还搞出AIGLX这种怪物。要我是ATI的人我也懒得给开发什么X驱动。
期待Wayland。

OpenGL: 3D graphics specification from SGI, descended from an earlier product
called IRIS GL, competitor of Direct3D and QuickDraw3D (deceased). Frequently
abbreviated "GL", particularly on Linux, since "OpenGL" is a trademark, and
use of the trademark requires passing a (non-free) conformance suite.

GLX: GL is a graphics language, not a windowing system. "GLX" refers to the
extension that binds GL to the X11 window system, enabling 3D drawing on X
windows. GLX is an extension to the X protocol. There are similar bindings
for other window systems too - WGL on Windows, AGL on MacOS. In X, the client
side GLX library is called libGL, and the server side extension is called
libglx.

Direct rendering: There are two ways a GL program can get its drawing done.
Either the client can do the drawing itself, or it can pass the GL requests
to the server and have the server do the drawing. Server-side rendering is
called "indirect rendering", and client-side rendering is called "direct
rendering". Direct rendering is usually faster. Historically, indirect
rendering was much slower in Xorg than direct rendering, because the indirect
renderer was entirely software. Since AIGLX, it's now merely a little slower.

DRI: The Direct Rendering Infrastructure is a technology that enables
direct rendering for GL programs on Linux and BSD operating systems.

Mesa: Mesa is a work-alike implementation of GL written by Brian Paul and
dozens of contributors. It contains a software rasterizer, a GL state machine,
and bindings to several window systems including X and Win32. All the open-
source DRI drivers are based on Mesa, as well as several closed-source DRI
drivers.

DRI driver: This is where all the excitement happens. The DRI driver is
responsible for programming the 3D hardware. Usually DRI drivers use the
Mesa state machine. In the DRI, the GLX client-side library loads a DRI
driver, named something_dri.so.

DRM driver: This is the kernel-side component of the DRI. The DRM is
responsible for security and handling resource contention. Not particularly
interesting, but mandatory. These are named something.ko in Linux 2.6.

DDX driver: This is a part of the X server, responsible for the other sorts
of X drawing like Render and Xv. The DDX has to be DRI-aware, but otherwise
not much GL-related happens in the DDX.

AIGLX: Accelerated indirect GLX. A feature that means the X server can load
a DRI driver, and use that to process indirect GLX protocol.

AGP: AGP is a fast version of the PCI local bus, with additional features
for graphics hardware. The core AGP kernel module is called agpgart.ko.

AGP chipset: Different motherboards have different chipsets and thus
different implementations of the AGP feature set. You need the one
corresponding to your motherboard chipset. This is not always the same as
your video chipset. Via chipsets need via-agp.ko, etc.

DRI2: Second version of the X server's DRI management protocol. Assumes more
kernel awareness of various objects than DRI1 did, which enables more things
to work correctly (redirected GLX and Xv most importantly).