Subject: Re: Success: X11 on Rage Pro and Rage I/II
To: Jochen Kunz <jkunz@unixag-kl.fh-kl.de>
From: Michael <macallan18@earthlink.net>
List: port-sparc64
Date: 06/02/2005 08:06:28
--Signature_Thu__2_Jun_2005_08_06_28_-0400_POzvfDUi7zZ8b/u3
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> Finaly I found time to do the promised testing... I own a U5 (Darwin+
> / Rage Pro) and a U10 (Darwin / Rage I/II). I run -current (last cvs
> updated May 20) with xsrc (last cvs updated May 23) on them. Beside
> mysterious problems with SCSI disk access I was able to run X11 on
> both of them out of the box. I only needed a litle bit vi(1) the
> XF86Config to adjust HorizSync, VertRefresh and DefaultColorDepth. The
> Rage Pro runs at 1280x1024 and the Rage I/II 1152x864, both at 16 bit
> clolor depth.

That's good to know - did you get any weird blitter errors, like things
not drawn at the right places, garbled text or so on the Rage II?

> The Rage Pro is knowen to work for some time. I can do some additional
> testing on the Rage I/II machine if needed. But the Rage I/II machine
> will be available for testing only until Saturday morning.

Please prod it a bit more under XFree if you have the time, and please
send me the dmesg output and XFree86.0.log - others definitely have odd
problems with the Rage II, if it works fine for you I'd like to see if
it's a different hardware revision or something like that.

> I have a UPA framebuffer 501-4789 Creator Series 3 (FFB2+) available
> for testing in the U10 too.

Should Just Work(tm) now, also with acceleration. I also added support
for virtual consoles which needs some more testing ;)

> Also: I got a U1e with 501-4127 Creator Series 1 (FFB) last weekend
> that I can use for tests. NetBSD 3.99.3 recognizes this card as:
> ffb0 at mainbus0 addr 0xffb5a000: Creator3D, model SUNW,501-2633,
> dac 10

Same as above, just make sure you have the latest source.=20
To define an ffb in XF86Config all you need is this:
Section "Device"
	Identifier "Creator"
	Driver "sunffb"
	BusID "SBUS:fd0"
Endsection

... and refer to it in the Screen section as
Device "Creator"

XFree apparently thinks 'SBus' is synonymous to 'use /dev/fb*', that's
why the ffbs and afbs are defined as SBus devices even though they're
not.

have fun
Michael

--Signature_Thu__2_Jun_2005_08_06_28_-0400_POzvfDUi7zZ8b/u3
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQp72RMpnzkX8Yg2nAQKwBggAuIdvbJiohUauzamDcJOY//k4IJiIOP1G
QpC6AFoBExwt/c/A0VF7qJLSICb9I7jZmOmCwbKhxpFv3KyeHZ5xvUD610j1ked5
dKrwxjZmwsyUe/UHf/yYvvkWZ4cE0nOA3tYtgch1VT20jvk7BVCmvY4fBAM7q1iO
S5nRSWTw7mjb5CTub7UmNJrL+K83/0eDzBnJ3JKiXoV+EkBBMfOHvBxqH3OeM0/H
29deYzRxt8dtYcmvMtGK/g9f2sAT4rUWVLd0XBfieHDZ2Zjl9EZ30sK/OZeibTQA
YQUQNCkLx8mPrU9NNdAGZvv5zYhkcJySnU0BZFKmk3jHeaCeTtfDgw==
=AqfR
-----END PGP SIGNATURE-----

--Signature_Thu__2_Jun_2005_08_06_28_-0400_POzvfDUi7zZ8b/u3--