-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 11 Aug 2005, Ferris McCormick wrote:
| 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.
That is new information for me; I had been led to believe otherwise, and
I have not been in a position to verify for myself. Thanks.
The few times I have tried this, I hadn't been using that screen res/combo
so that could be a problem.
mach64 shows up a few ways on SPARC which can make life tricky. In the
Ultra 5/10 boxes, it comes as an onboard framebuffer in either 2MB or 4MB
RAM sizes depending on the age of the box. Similarly, the Blade 100/150
has a mach64 with 8MB of RAM onboard (which is what I tested DRI on many
moons ago). Also there is the PGX24 framebuffer IIRC which is a PCI card
version of the mach64 that can be used in machines like an Ultra 30 or 60
where there is no onboard framebuffer.
Another note is that the radeon driver should probably be considered for
the DRI list as the XVR-100 Sun framebuffer is a rebranded ATI Radeon 7000
VE. I have one I can test with/on once I get back from LWE.
Cheers,
- --
Jason Wever
Gentoo/Sparc Co-Team Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC+uyAdKvgdVioq28RAvefAKC2MrZSO5O89ui/DYf6WLg+F2Ui5wCgohXd
AJIIytvNXCV7nU8/IOzFjTA=
=lnRz
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
