generic RFKILL support

[Dan Williams]

On Thu, 2009-04-23 at 17:13 -0400, eye zak wrote:
> Hi all,
> 
> I am writing rfkill support into the ath5k driver, and I have a
> issue/bug. When I remove my module, the rfkill /sys device is removed
> but hal leaves it as an orphaned (fields are missing and name is null)
> rfkill switches.  I do iterate in number as i remove and add my module
> repeatedly (rfkill0,1,2) but that is due to the phy incrementation and
> should be unrelated. After several modprobe/rmmod cycles i now have
> many unorphaned rfkill devices in hal.  How can I get rid of them, or
> is it a bug in HAL?
> 
> .fdi support is also missing for a generic rfkill switch (maybe one
> big one with exeptions ?) so I had to add one for my specific device.
> The changes are not accepted upstream yet so I won't post my file.

They should be supported already with HAL 0.5.12 at least.  There's
generic rfkill support already there (hald/linux/device.c and
hald/linux/addons/addon-rfkill-killswitch.c).  I assume that's not
working for you?

BTW the issue with killswitches not being torn down could be a udev bug.
Run 'udevadm --monitor' and rmmod your module, then reply with the udev
output so we can see whether udev is doing the right thing.  If it's
not, it may indicate a problem in the kernel's rfkill layer.

dan