Kernel Bug Tracker – Bug 11928
ath5k gets lost with eeepc-laptop removal
Last modified: 2008-12-01 15:13:32 UTC
Subject : ath5k gets lost with eeepc-laptop removal
Submitter : "Luiz Fernando N. Capitulino" <firstname.lastname@example.org>
Date : 2008-10-31 13:05
References : http://marc.info/?l=linux-kernel&m=122545827204957&w=4
Handled-By : "Nick Kossifidis" <email@example.com>
Notify-Also : Matthew Garrett <firstname.lastname@example.org>
Notify-Also : Alan Jenkins <email@example.com>
This entry is being used for tracking a regression from 2.6.27. Please don't
close it until the problem is fixed in the mainline.
This is how the rfkill interface to the hardware behaves. It's not a bug.
Matthew I see your point, but IMHO it doesn't seem acceptable to loose the device when the module is removed.
If it's not a bug we could at least have a workaround for it.
The only workaround would be for the rfkill core not to disable the radio on unregistration.
No way. We will remain disabling the radio on unregister. It is a safety thing.
It can be worked around in eeepc-laptop itself in various ways, although I would recommend against it.
You can have an in-driver flag that you can set before calling the unregister hook, to error out instead of disabling the radio in your toggle_radio() hook,
for example. Or you could manually re-enable the radio in your driver after
unregistering (which is probably even more annoying than leaving it disabled).
If this was thinkpad-acpi, I would document the platform weirdness, add a DEVELOPER kconfig option to enable the "filter the unregister radio block command" functionality (so as to make it easier on people who need to keep loading/unloading the module) with a suitable printk to know it was enabled when requesting debug logs, and leave it at that.
Notify-Also : Luiz Fernando N. Capitulino <firstname.lastname@example.org>
On Sunday, 9 of November 2008, Matthew Garrett wrote:
> It shouldn't be listed as a regression.
Dropping from the list of recent regressions.
What's the status of this bug report? I fail to see agreement so far. Is it not an issue?
Any updates? If not this should be closed....
Well, I think it's up to Matthew to decide.
This doesn't bother me so much any more. If he thinks that this is not an issue this can be closed.
We've been wanting to help here but no replies yet so will be closing this. Please open the bug up if you decide it is and if so lets get to fixing it.