On Mon, Nov 30, 2009 at 05:37:04PM -0800, Dmitry Torokhov wrote: > On Tue, Dec 01, 2009 at 02:28:06AM +0100, Kay Sievers wrote: > > On Tue, Dec 1, 2009 at 00:27, Johannes Stezenbach <js@xxxxxxxxx> wrote: > > > + strncat(fn, "/device/device/force_release", sizeof(fn)); > > > > You can only select a parent device by it's subsystem/devtype. Any > > hardcoded assumption about the order of parents is wrong, and the > > "device" link is deprecated, it must not appear anywhere in udev code. I have to admit I have no clue how else to do it. I'd be glad to hear your advice. > Maybe the quirk should fire up for /sys/device/platform/i8043/serioX > devices to begin with and not go backwards from the child event device? Good point. Maybe it doesn't make sense to handle the quirk in keymap.c then, but rather add its own utility to be called from a seperate udev rule for SUBSYSTEM=="serio"? If yes, does it still make sense to add the force_release flags to the keymap files, or is it better to use a seperate file which just lists the keys which should be added to the force_release quirk? Thanks Johannes -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
