On Wed, 13 Oct 2004 16:39:27 +0100, Keith Whitwell <[EMAIL PROTECTED]> wrote: > So, it's not really an unimplemented poll() function, but the > backwards-compatible ghost of a real communications channel which is still > polled, but never written to.
One way to fix this would be to alternately return (POLLIN | POLLOUT | POLLRDNORM | POLLWRNORM) and zero. For a normal poll function zero means that data is not ready and to keep on polling. If we alternate between the two a correct polling program would get the zero, and then poll again and get POLLIN.. and work. If X tries the poll function it will get POLLIN.., retry and get zero, so it should work too. Will the current X code retry on a non-zero return? Can we fix the X server to remove this code in the future? Or fix the X server to set a higher interface number and change behavior based on the interface number? Right now I removed the polling code from DRM and the OS defaults took over. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
