Re: evdev* devices change major/minors after suspend/resume (udev?)
Zitat von Soeren Sonnenburg <[EMAIL PROTECTED]>: > > Very concrete it is this evdev that may be missing... and just FYI this > also seems to cause trouble in Xorg - sometimes the appletouch mouse is > not yet back... > > /dev/input/by-id/usb-Apple_Computer_Apple_Internal_Keyboard_._Trackpad-event-kbd > -> ../event5 > > Any hints welcome, See also this discussion thread: http://www.uwsg.iu.edu/hypermail/linux/kernel/0703.3/0988.html But there is no solution for this problem right now. with kind regards thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
evdev* devices change major/minors after suspend/resume (udev?)
Dear all, I wonder how one (from the userspace side) should deal with the case that evdev devices disappear after resume and reappear under a different name/different major/minor (i.e. evdev1 can become evdev4). The application in mind scans all evdev devices, opens the ones matching certain properties and then processes events on them. Now the problem is that after resume devices disappear, so the application rescans+reopens the evdev's BUT some of the evdevs are just not available right after resume but appear at some point later in time. Is there a way to wait till all evdev's are recreated / ask for udev to settle ? Or what is the proposed way of dealing with that ? Very concrete it is this evdev that may be missing... and just FYI this also seems to cause trouble in Xorg - sometimes the appletouch mouse is not yet back... /dev/input/by-id/usb-Apple_Computer_Apple_Internal_Keyboard_._Trackpad-event-kbd -> ../event5 Any hints welcome, Soeren -- Sometimes, there's a moment as you're waking, when you become aware of the real world around you, but you're still dreaming. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
evdev* devices change major/minors after suspend/resume (udev?)
Dear all, I wonder how one (from the userspace side) should deal with the case that evdev devices disappear after resume and reappear under a different name/different major/minor (i.e. evdev1 can become evdev4). The application in mind scans all evdev devices, opens the ones matching certain properties and then processes events on them. Now the problem is that after resume devices disappear, so the application rescans+reopens the evdev's BUT some of the evdevs are just not available right after resume but appear at some point later in time. Is there a way to wait till all evdev's are recreated / ask for udev to settle ? Or what is the proposed way of dealing with that ? Very concrete it is this evdev that may be missing... and just FYI this also seems to cause trouble in Xorg - sometimes the appletouch mouse is not yet back... /dev/input/by-id/usb-Apple_Computer_Apple_Internal_Keyboard_._Trackpad-event-kbd - ../event5 Any hints welcome, Soeren -- Sometimes, there's a moment as you're waking, when you become aware of the real world around you, but you're still dreaming. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: evdev* devices change major/minors after suspend/resume (udev?)
Zitat von Soeren Sonnenburg [EMAIL PROTECTED]: Very concrete it is this evdev that may be missing... and just FYI this also seems to cause trouble in Xorg - sometimes the appletouch mouse is not yet back... /dev/input/by-id/usb-Apple_Computer_Apple_Internal_Keyboard_._Trackpad-event-kbd - ../event5 Any hints welcome, See also this discussion thread: http://www.uwsg.iu.edu/hypermail/linux/kernel/0703.3/0988.html But there is no solution for this problem right now. with kind regards thomas - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
