comparis
In-Reply-To: <2528301.1176437111491.JavaMail.Twebapp at oss-app1>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OpenSolaris-URL:
http://www.opensolaris.org/jive/message.jspa?messageID=109810&tstart=0#109810
I hope my wsfb criticism didn't sound too negative, I myself don't know it any
better, either.
And I know you haven't too much different hardware available for compatibility
testing.
Last night's experiments do confirm, that wsfb is indeed the best base for the
purpose of creating such a universal fallback-driver.
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)
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
One would currently get "invalid ioctl()" on a PGX32, with /dev/fb linking to
/devices/pci at 8,700000/TSI,gfxp at 3:gfxp0
But a fix is under way.
This message posted from opensolaris.org
