On Sun, Apr 26, 2009 at 21:54, Marco d'Itri <m...@linux.it> wrote:
> Is this reasonable?
> With udev 0.140 (or rather: sometime after 0.125) we've lost the
> persistent device symlink /dev/input/by-path/platform-gpio-keys-event-
> due to the following change in 60-persistent-input.rules which no longer
> allows an empty ID_CLASS:
> It seems to me that the simplest solution is to let udev define a class
> for gpio-keys (kbd seems most logical), for example with the following
> change in 60-persistent-input.rules:
>
> -DRIVERS=="atkbd", ENV{ID_CLASS}="kbd"
> +DRIVERS=="atkbd|gpio-keys", ENV{ID_CLASS}="kbd"
I guess, this is any key on a system board, and is not like the usual,
pretty well defined "kbd".
For path links of platform devices, we should just create a:
/dev/input/by-path/platform-gpio-keys-event
link, which should be fine as long as there is only a single interface
per platform device. USB devices should also be fine in having this
link, because they include the interface number in the path name.
I've committed a change along with some other pending changes to the
git repository.
Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
