Hi Ivo, > The rfkill driver I had previously posted on the netdev list has been revised > and nearly completed. It only needs some testing, but the current behavior > now exactly what is described above.
Nice :) > rfkill displays the status that the button has to userspace, > the user is allowed to toggle the radio on or off, _only_ when he toggling > the radio to the state that the hardware button indicates. > So the radio cannot be enabled while the button is set to Off. Are you sure no one will come up with hardware where the button is a simple touch button and software can toggle as well? In that case, we'd need a flag somewhere for 'software button control'. It seems better to add this flag to the userspace interface now than retroactively when needed because then all applications using it would need to be updated. > But it will only request the toggling of the radio, the interface can still > excist and the state of the radio of the interface can be requested at any > time > as well as the state of the button. Right. For bcm43xx, this makes perfect sense. > I'll soon send rfkill to the netdev list for a second feedback round, before > I submit > it to be applied to the kernel tree. Great! johannes
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
