> So, please accept my appologies on the tone of the last email. Please > reconsider reading that email in full, and please try to ignore the rantness > smell in it. I did try to explain the technical reasons why some changes > would be needed in b43. Ok. I actually did read it but decided not to reply to most things. I don't think it's that everybody needs to be educated on the input layer (I've written real input drivers before) but rather that nobody really knows how userspace/kernel interaction wrt. rfkill should work. > > To address one point though: userspace does want a notification when the > > hw-rfkill is activated so it (e.g. network manager) can ask people to > > un-rfkill their device. > > I tried to add such notifications directly to the rfkill class. rfkill now > issues uevents and calls a notification chain for any state changes. It has > been modified to differentiate hw-rfkill from sw-rfkill, and export that > information to userspace for network-manager and other applications to use. Sounds good. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
