| Message ID | 201308130055.29423.s.L-H@gmx.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
--- a/drivers/input/misc/wistron_btns.c +++ b/drivers/input/misc/wistron_btns.c @@ -971,6 +971,7 @@ static const struct dmi_system_id __init }, { NULL, } }; +MODULE_DEVICE_TABLE(dmi, dmi_ids); /* Copy the good keymap, as the original ones are free'd */ static int __init copy_keymap(void)
This allows the wistron_btns module to be autoloaded on boot, its functionality is required to support the hardware rfkill switches on most of the supported notebooks, in order to unblock the hard blocked rfkill state for wireless and bluetooth devices. Tested on a Medion MD96500: alias: dmi*:svn*MEDIONPC*:pn*WIM2040*: Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> --- This patch may be considered RFC, while it is certainly the right thing to do, some of the DMI matches might be a bit wide, e.g.: dmi*:svn*FUJITSUSIEMENS*:pn*AMILOD*: dmi*:svn*FUJITSUSIEMENS*:pn*AmiloD*: dmi*:svn*FUJITSUSIEMENS*:pn*AMILOM*: all others are very targetted - and I haven't noticed any issues by forcing wistron_btns on system not requiring it so far. drivers/input/misc/wistron_btns.c | 1 + 1 file changed, 1 insertion(+) -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html