Hi On Tue, Apr 7, 2015 at 1:40 PM, Hans de Goede <hdego...@redhat.com> wrote: >> The series looks reasonable, but I wonder why we cannot merge it into >> 60-keyboard.rule (60-evdev.rule now) like Peter's series does? In that >> case, please make this a builtin of input_id which uses >> udev_device_get_parent_subsystem_devtype() and look for the >> serio/atkbd (?) parent device, instead of hard-coding the path. > > > Why would we want to merge this into keyboard rules/hwdb? Trackpoints > always have a separate driver, input device and event node.
Right now, we do hwdb lookups for keyboard:foobar, evdev:foobar and now trackpoint:foobar, instead of a single lookup for evdev:foobar. To me, it looks much easier if we have one generic evdev rule, which searches the hwdb based on the input-modalias via evdev:input:<modalias> and the legacy fallback, evdev:name:<name>:<dmi> Depending on what properties where found, we simply apply them to the evdev node. Thanks David _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
