Subject: Re: XF86 wsfb driver and wscons ioctl
To: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
From: Michael <macallan18@earthlink.net>
List: tech-x11
Date: 01/17/2005 07:33:38
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>
Hello,

> I take a look at some source files, but I'm afraid current wsfb driver
> is still problematic.
>
> - wsfb uses WSDISPLAYIO_LINEBYTES ioctl() and WSDISPLAYIO_MODE_DUMBFB
>   flag for WSDISPLAYIO_SMODE to mmap(), but they were added after 2.0
>   was branched.
> - Only sparc64/dev/ffb.c supports these new ioctls, doesn't it?
That may well be - machfb and macppc's ofb certainly don't.
Although my extended ofb monitors WSDISPLAYIO_SMODE to do some cleanup 
when the Xserver exits.

> - IMHO, these ioctls (taken from OpenBSD?) seem really stupid.
>   I think we should have more generic ioctl which returns whole info
>   about MI rasops(9), which includes screen size, bitmap vaddr
>   for mmap(), depth, and stride etc. rather than limited ioctls for
>   LINEBYTES, DUMB or so.
Agreed.
There's WSDISPLAYIO_GINFO, maybe it should be extended a little. I'm 
not sure how generic this is but ofb (and therefore machfb too) maps 
the framebuffer when you mmap something between 0 and VRAM_size ( or 
aperture_size ) and additionally whatever it finds in OF's 
addigned-addresses property which more or less corresponds to the PCI 
BARs.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBQeuwospnzkX8Yg2nAQL6pQf+KuQbtF2ucSuv63sqQFZ/WDyEYX7ABY3x
i5g0x5lqhUvhxCwOa72ArnWv85akHAfMjxxWeu1KQGLMst1F1jwVnZZiFoZYhPgv
nYqYXhZ1kS1HXt0amn6RSJuff6mv5ARRwI2R5RM8JAoqpTm2qUCDt+fHSL8o0z5r
FiGtbAmI4au0kIvif9hSeV5zUf8ri6HswtQUH79kmk8xPBZTCy3EsAcs3unH/ZdL
M0mUgLvQKsEts3IPYP+I71rh7zlYkO75XlJdtyVohXCJqHjpDw1v5iUY3Qqag7Ww
2D9SB1nJ/MsIINmU1jVY42uhvFJvmSx0dzaj0rO4qCnJ0eLn0kH6ag==
=lemK
-----END PGP SIGNATURE-----