>> >> A couple of years ago, any attempt to return anything else than 0 from >> drm poll resulted in an X server error. >> http://freedesktop.org/bugzilla/show_bug.cgi?id=1505. The fix mentioned >> in the bug was actually to return 0 from drm poll, and a comment about >> this is still present in drm.git. The above breaks drm for old X servers >> and all drivers, which I think is against drm policy? > > That can't be the real problem. The X server polls on a ton of file > descriptors already; sockets from clients, dbus, input devices. They > all have poll implementations that don't return 0... I mean, otherwise > they wouldn't work. Look at evdev_poll() in drivers/input/evdev.c for > the evdev poll implementation, for example.
Its a very real problem otherwise we wouldn't have a bug open and an bodge around in the kernel to workaround the broken X servers. Since this stuff is reliant on kms perhaps just use an alternate poll for kms drivers that does it right. Dave. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
