Martin Bochnig wrote:
> One of my experiments (as I still don't have any Xsun sources [except for the
> DDK and sunInit.c]) : I found out, that Xsun doesn't have any device-specific
> knowledge at all. Nor does it perform any general bus scans (as I can see
> from comparing Xsun's sunInit.c versus in Xorg's init c file). I took Solaris
> 2.5.1's Xsun packages and tested them with /dev/fb drivers, ddx modules and
> actual hardware that came out 6 yours after that old Xsun server. But that
> vintage Xsun server from 1997 is still able to use drivers and hardware which
> didn't show up before 2003!!! This tells a quite lot about how the server's
> and the driver's sources must be (vaguely) organized. That's the first step
> in reverse engineering whatever. And the only option left when stuff is
> closed source, sigh ...
Right - all Xsun does is open /dev/fb (or whatever devices are
specified in -dev flags or the OWconfig file), call the
VIS_GETIDENTIFIER ioctl, and then look in OWconfig for which
ddx module to dlopen() for the returned value. We make no
changes to it for new platforms or busses. This even works
with the Sun Ray, which provides a /dev/fb device that responds
with a string that maps to their module, that then opens a network
connection to the frame buffer instead of a memory mapping.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
