Ville Syrjälä wrote:
>? Some fb drivers support the FBIO_WAITFORVSYNC ioctl (matroxfb and
>atyfb at least).
>
>
>
I searched a bit. In linux-fbdev there seem to be patches that implement
this for
radeonfb (2005-12) and intelfb (2006-06). Do you know if these have
been applied to 2.6.18?
It seems that a lot of people are interested in this and perhaps
FBIO_WAITFORVSYNC
could be moved to fb.h
BTW, DirectFB could do
#ifdef FBIO_WAITFORVSYNC
ioctl(..);
#else
while (inb() && --watchdog);
#endif
>
>
>
>>Does DirectFB use /dev/mem or other hacks that are disabled by
>>BSD Secure levels?
>>
>>
>
>I don't know what BSD secure levels do but I don't think so.
>
>
>
BSD Secure levels forbids various stuff depending on the level. In level 1
for example, it forbids CAP_RAWIO which is ioperm(), iopl() and access
to "dev/kmem", etc. The thing with BSDseclvl is that at this level, the
services are denied even to the superuser!
>>If I allow all users to rw /dev/fb0 and /dev/mouse, will it
>>work?
>>
>>
>
>The mouse device depends on which input driver you use. ps2mouse driver
>needs access to /dev/psaux, /dev/misc/psaux or /dev/input/mice. keyboard
>driver needs read access to /dev/tty0 and rw access to the current vt's
>/dev/tty? device. You can replace both ps2mouse and keyboard drivers
>with the linuxinput driver which needs rw access to /dev/input/event?
>devices.
>
>
>
Thanks.
jf
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
