[oops, meant to reply to this earlier, but overlooked it in my list of
messages to respond to.]
Martin Bochnig wrote:
> Alan Coopersmith wrote:
>> 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
>
> Yup, as starting circa in Solaris 2.5.1 (with X11R6), still the same? Cool.
>
>> ddx module to dlopen() for the returned value.
>
> Aha, thanks for confirming this. I assume next would be parsing OWconfig
> for the matching ddx specific xyz-fb_init() function and passing control
> to that function (and whatever it might do or call), therefore
> effectively switching into X11 mode?
Yes. I could probably release the libowconfig code for OWconfig parsing
fairly easily since it's a single .h & .c file if someone really wanted to
do that.
> Mhh, can't you (or anyone with access to the Xsun src [just throw it
> over]) build some custom Xorg-Xsun-hybrid, I mean some hybrid Xorg
> monster with Xsun's sunInic.c file. And all required symbols renamed to
> match Xsun-ddx's needs, such as globally renaming "sunInitThisOrThat()"
> to how Xorg uses to call the corresponding function?
But if we renamed the Xsun symbols, how would the existing DDX modules
call them?
The Xsun->XFree86 module bridge worked because XFree86 modules at the time
used a customized ELF format and custom loader, not just dlopen, so any
call through that loader went to the XFree86 version of the functions, not
the Xsun ones, and there was no symbol clash for the normal linker to deal
with. I'm not sure if the loader's object grouping functionality could
do something similar or not.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
