Subject: Re: CVS commit:
To: None <source-changes@NetBSD.org>
From: Michael <macallan18@earthlink.net>
List: source-changes
Date: 10/01/2005 13:10:14
--Signature_Sat__1_Oct_2005_13_10_14_-0400_6JSnKUp8ZENPc7yk
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Hello,
> Modified Files:
> xsrc/xfree/xc/programs/Xserver/hw/xfree86/drivers/wsfb:
> Imakefile
> wsfb_driver.c
> Added Files:
> xsrc/xfree/xc/programs/Xserver/hw/xfree86/drivers/wsfb: wsfb.h
> wsfb_cursor.c
>=20
> Log Message:
> Add hardware cursor support and the usual XF86Config options to turn
> it on and off, change the default device to ttyE0 ( since ttyC0 is a
> serial port on most SPARCs )
> This needs a wsdisplay driver which actually supports the
> WSDISPLAYIO_GCURMAX and WSDISPLAYIO_SCURSOR ioctls. Tested on
> NetBSD/sparc with igsfb on a JavaStation NC / Krups.
Hmm, sounds a bit ambiguous on 2nd glance - if the underlying wsdisplay
doesn't support a hardware cursor wsfb will just use a software cursor
as before. This relies on ioctl(WSDISPLAYIO_GCURMAX) to fail if there's
no HW cursor support. If a driver lies about its capabilities we have no
way to know about cursor support ( that's what Option "SWcursor" is for
)
have fun
Michael
--Signature_Sat__1_Oct_2005_13_10_14_-0400_6JSnKUp8ZENPc7yk
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)
iQEVAwUBQz7C+cpnzkX8Yg2nAQKlZwf9EL8/via5ghbwhPBnUnrSE8wiL/gGbadj
GBJKXnhzBJjXsFgb/ujzrT3nCcPa7VQ/88sTPJVIX8Jef/yvacAsml4aH+4fgfvc
slshw3eCJsvVZJDguyJsl0l/f/LbmL6w76fzz4cz2944tppDw9kVecyqoJPZGP7i
Xj+3DacGYjhLtE8inKLViF7v1SZ2E3zShpmq0EKQGl9whTZIK7IxDF+iSykfRyph
99d1HnMBXZnXjgTzpdahxQQvK0hBdQO3gbC+KE9RA2OBXPvPORn9qDi5LJJysj5c
7IjQTdXGnwxF6sOphJKldh/gWIcalnatAnOHueGpzO3YTKFhr+sukg==
=e9yy
-----END PGP SIGNATURE-----
--Signature_Sat__1_Oct_2005_13_10_14_-0400_6JSnKUp8ZENPc7yk--