From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: evdev* devices change major/minors after suspend/resume (udev?)
Date: Wed, 11 Apr 2007 11:20:47 +0200 [thread overview]
Message-ID: <1176283247.14106.10.camel@localhost> (raw)
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.
next reply other threads:[~2007-04-11 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 9:20 Soeren Sonnenburg [this message]
2007-04-11 15:01 ` evdev* devices change major/minors after suspend/resume (udev?) thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1176283247.14106.10.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox