On Tue, Oct 19, 2010 at 1:15 PM, Joey Lee <jlee@xxxxxxxxxx> wrote: > Hi Corentin, > > æ äï2010-10-19 æ 12:51 +0200ïCorentin Chary æåï >> >> Most of users will want the key to just toggle wlan/bluetooth. But some of them >> >> will be happy if they can configure the behavior of the key (cycle, only toggle >> >> WLAN, etc...) >> >> >> > >> > I thought just direct disable the default EC behavior then leave a >> > userland daemon to control the behavior, it will grab the wifi key event >> > then control rfkill state by follow user's customization rules. >> >> What I'm saying is: I don't really care what's the default behavior is, >> but if the EC provide a somewhat reliable way to make the key work >> without any userspace daemon involved, I think we should allow >> the user to use this mode (even if it's with an obscure module >> parameter or sysfs file). >> >> But .. maybe if someone want this default "raw" behavior, >> he should just not load this module. >> > > Fully understood, now. > > Like you siad, we need define a policy for: > > Â- If user want the default "raw" behavior, what do they need to do? > Â Â Â ÂI thought if the wmi driver doesn't load by default, then user > Â Â Â will get a "raw" behavior. > > Â- If any distro want provide userland solution, how can they disable > Â the default "raw" behavior? > Â Â Â ÂIf anybody want to disable the "raw" behavior, just load the wmi > Â Â Â driver. > > Does it right? Yeah, seems to be ok... -- Corentin Chary http://xf.iksaif.net -- 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
