Dmitry, On Tuesday 22 January 2008 00:55:37 Carlos Corbacho wrote: > Shoving some printk's into input.c shows that it fails in > input_match_handler() on: > > id = input_match_device(handler->id_table, dev); > if (!id) > return -ENODEV; > > This test always fails for every call of input_match_handler() in > input_register_handler(). > > Unloading and reloading rfkill-input then somehow causes this test to not > fail, and rfkill-input is then properly registered... Any thoughts at all on how to diagnose why rfkill-input is not able to find a device to attach to the first time it loads (or more specifically, why input_match_device() fails to return a match the first time around), because I'm still scratching my head on this four months later... -Carlos -- E-Mail: carlos@xxxxxxxxxxxxxxxxxxx Web: strangeworlds.co.uk GPG Key ID: 0x23EE722D -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
