On Monday 09 Jan 2012 14:31:17 Lee, Chun-Yi wrote: > From: "Lee, Chun-Yi" <jlee@xxxxxxxx> > > Have many non-acer machines have AMW0_GUID2 method in DSDT, in > original acer-wmi design, driver direct set ACER_CAP_WIRELESS flag > for those machines but didn't check the functionality for set/get > wireless state. > It causes acer-wmi driver create a broken wireless rfkill and it > already set to soft blocked. > > So, this patch add a wireless capability check before we set > ACER_CAP_WIRELESS flag to the machines that were included AMW0_GUID2. > It avoid acer-wmi create a broken wireless rfkill. > > Thank's for Matthew Garrett give the idea. > > Reference: brc#674353 > https://bugzilla.redhat.com/show_bug.cgi?id=674353 > > Tested on Lenovo E520. > Tested on Acer TravelMate 4750. Is there really no other way to detect the availability of wireless on hardware with that GUID without resorting to poking stuff to see if it sticks? My assumption has always been that there must be of finding out, but I've never had the hardware to check that with. -Carlos -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
