Michael, you mean "port within MESA radeon module, without touching my DRI kernel module. Correct? Thanks! Luigi P.S. - can it be the case that ATI cards are all out of MESA miniglx support? If you take a look at the DRI classifier, almost all the PCIe cards are classified as NEW_MEMMAP.. <div class="gmail_quote">On Thu, Apr 10, 2008 at 11:17 AM, Michel Dänzer <<a href="mailto:michel@tungstengraphics.com">michel@tungstengraphics.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Thu, 2008-04-10 at 11:13 +0200, Luigi Campora wrote: > > Apr 7 11:13:46 localhost kernel: [drivers/char/drm/radeon_cp.c,1767: > ENTERING radeon_cp_init cmd=80546440,data=78ddac78 > Apr 7 11:13:46 localhost kernel: [drm:radeon_do_init_cp] *ERROR* > Cannot > initialise DRM on this card > Apr 7 11:13:46 localhost kernel: This card requires a new X.org DDX > for 3D > > Indeed, the card is described as a "NEW_MEMMAP" card in the > drivers/char/drm > directory, but there's no mention within Mesa code to any ioctl's > filling > that > new_memmap param via a RADEON_SETPARAM_NEW_MEMMAP request. </div>Looks like you need to port the corresponding code from the xf86-video-ati radeon driver then. -- Earthling Michel Dänzer           |          <a href="http://tungstengraphics.com" target="_blank">http://tungstengraphics.com</a> Libre software enthusiast         |          Debian, X and DRI developer </blockquote></div>