eeepc-laptop rfkill, stupid question #4 and 5
- From: Alan Jenkins <alan-jenkins@xxxxxxxxxxxxxx>
- Date: Fri, 31 Oct 2008 17:09:09 +0000
Did you miss a call to rfkill_force_state() on resume?
I can hibernate, then interrupt the boot with F2 to get into the BIOS,
change the "Enable WLAN" setting, and continue the resume. When the
eeepc-laptop driver resumes, it restores the pre-hibernation value.
Actually, normal boot doesn't preserve the setting either. Your commit
changes the behaviour from the rfkill state being persistent across
reboot / power off (as a bios setting), to being always enabled on
boot. It seems like a bad idea to me.
Thanks
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: eeepc-laptop rfkill, stupid question #4 and 5
- From: Matthew Garrett
- Re: eeepc-laptop rfkill, stupid question #4 and 5
- Prev by Date: Re: [PATCH] Add io-mapping functions to dynamically map large device apertures
- Next by Date: Re: sched domains oddness.
- Previous by thread: alpha: undefined reference to `save_stack_trace'
- Next by thread: Re: eeepc-laptop rfkill, stupid question #4 and 5
- Index(es):
Relevant Pages
|