-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ferris McCormick wrote: | I wrote the note very fast, and it was not too clear. With sunffb, the | kernel code for current 2.6.x (x > 6) is broken, and davem has taken dri | support out of the xorg sunffb driver (to paraphrase him, you can't do | both drm and correct font rendering).
OK, it might be nice to bring alanh in on this conversation since he recently fixed up the ffb DRI code, also to retest with the new code. And as far as davem taking out DRI from the DDX code, that seems easy enough to re-enable and test again -- just #if 0 changed back to XF86DRI. [EMAIL PROTECTED] /usr/local/share/xorg/modular/driver/xf86-video-sunffb/src $ grep -i xf86dri * ffb_dri.c:#define _XF86DRI_SERVER_ ffb_driver.c:/*#ifdef XF86DRI*/ ffb_driver.c:#if 0 /*def XF86DRI*/ ffb_driver.c:#if 0 /*def XF86DRI*/ ffb_driver.c:#if 0 /*def XF86DRI*/ ffb.h:#ifdef XF86DRI ffb.h:#ifdef XF86DRI ffb.h:#ifdef XF86DRI ffb.h:#ifdef XF86DRI | With mach64, the problem on sparc has been the hardware itself, if I | remember correctly. That is, kernel, xorg are fine, but the mach64 card | used on U5/U10 is memory-deficient. Someone who has looked at it more | recently than I have will correct this. (There is a mach64-based sparc | frame buffer which should be OK for DRI, but I've never seen one. I'll | chase it down in the framebuffer handbook a little later.) My u5 works just fine with DRI at 800x600 resolution, 16-bit color. Any higher than this and you're right, not enough memory. | Changing DRI_DIRS is exactly what I did. Not really... DRIVER_DIRS != DRI_DIRS e.g., DRIVER_DIRS = dri, DRI_DIRS = mach64 ffb Thanks, Donnie -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC+oMZXVaO67S1rtsRAr4zAJ9pdiE+OY9olRg3iLet8TPZ+cc0LACgz2nc Z+702RsgsYdWHvYWoErTeaE= =Wo8g -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
