On 7/30/06, Valdis.Kletnieks@xxxxxx <Valdis.Kletnieks@xxxxxx> wrote:
If the program says '100ms' because it knows it will need to do a GUI update then, and you block it for 5 seconds because that's when the next value update happens, the user is stuck looking at their gkrellm or whatever not doing anything at all for 4.9 seconds.... This almost forces the use of multiple threads if the program wants to do its own timer management.
Please read my detailed proposal, posted (and resivsed) later. The program is not blocked by the new ioctl, it still does a poll() or select() and can provide a timeout, as usual. The only trick is that the poll() won't return with an input-ready event until the appropriate time. Shem - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
