Johannes Berg skrev:
On Fri, 2009-07-17 at 02:35 +0300, Thomas Backlund wrote:
So far so good. Your platform's soft-switch is wired to the card's hard
kill line. Mind trying
./rfkill unblock 0
(or whatever ID the acer-wireless has) at this point to see what
happens? I would hope it goes back to the working state.
Nothing happends...
It does not change anything on either acer-wireless or phy0
Humm. Can you try this?
johannes
--- wireless-testing.orig/drivers/platform/x86/acer-wmi.c 2009-07-17 00:19:20.000000000 +0200
+++ wireless-testing/drivers/platform/x86/acer-wmi.c 2009-07-17 01:58:11.000000000 +0200
@@ -973,7 +973,7 @@ static int acer_rfkill_set(void *data, b
{
acpi_status status;
u32 cap = (unsigned long)data;
- status = set_u32(!!blocked, cap);
+ status = set_u32(!blocked, cap);
if (ACPI_FAILURE(status))
return -ENODEV;
return 0;
Funny how easy the fix was...
Now the rfkill works... ;-)
I can enable/disable it as many times as I want...
So it's:
Tested-by: Thomas Backlund <tmb@xxxxxxxxxxxx>
The difference is that before this patch, bluetooth & wireless were both
disabled at boot...
With this patch the system boots up with bluetooth & wireless is enabled
by default (But it's not a regression as it now behaves just like 2.6.29
& 2.6.30 series kernels)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
