Hi Carols, On Sun, Apr 13, 2008 at 12:23:12PM +0100, Carlos Corbacho wrote: > On Saturday 12 April 2008 18:21:31 Carlos Corbacho wrote: > > 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... > > I think I've found the problem here. > > rfkill-input isn't being attached to a device because it's looking for > KEY_WLAN. The problem is that at boot time, I don't have a KEY_WLAN - the key > isn't mapped until HAL & hal-info kick in much later. > > I've tested this by blacklisting rfkill-input, waiting until HAL has loaded > and run setkeycodes, and then loaded rfkill-input, which then works properly > first time round. > > Unfortunately, that's only a workaround, not a real solution, so we're going > to need a better way of handling this case. > Yes, setting KEY_X later, after registering input device will not cause device/handler rescanning. We'll have to do something about it now that we recommend using HAL to update keymaps properly. -- Dmitry -- 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
