Martin Bochnig wrote:
> Further, a minor correction to my previous email:
> wsfb does not depend on ioctl()'s (not plural), but only on a single
> problematic one (in the sense of being device specific) :
> $ grep -n FBIOGXINFO ./*
> wsfb_driver.c__ORIG:410: if (ioctl(fd, FBIOGXINFO, &fbinfo) ==
> -1) {
> wsfb_driver.c__ORIG:525: if (ioctl(fPtr->fd, FBIOGXINFO, &fbinfo) ==
> -1) {
> wsfb_driver.c__ORIG:527: "ioctl FBIOGXINFO: %s\n",
> wsfb_driver.c__ORIG:1090: if (ioctl(fPtr->fd, FBIOGXINFO,
> &fbinfo) == -1)
Several graphics devices support it, but not all.
> And it wasn't m64, but pfb (ATI-Radeon_/_XVR-100) :
> bash-3.00$ strings /platform/sun4u/kernel/drv/sparcv9/*|grep FBIOGXINFO|wc -l
> 1
> bash-3.00$ strings /platform/sun4u/kernel/drv/sparcv9/pfb|grep FBIOGXINFO|wc
> -l
> 1
> bash-3.00$ strings /platform/sun4u/kernel/drv/sparcv9/pfb|grep FBIOGXINFO
>
> FBIOGXINFO
Wouldn't it have the numeric value of the FBIOGXINFO #define from
/usr/include/sys/fbio.h instead of the string anyway?
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
