On Mon, 2009-06-01 at 16:47 +0200, Marcel Holtmann wrote: > > This adds the two following things to /dev/rfkill: > > 1) notification to userspace with a new operation > > RFKILL_OP_NVS_REPORT about default states restored > > from platform non-volatile storage > > I really don't understand why this is needed. What benefit does it give > us compared to just sent OP_CHANGE and OP_CHANGE as an update. My X200 > for example does this anyway on suspend/resume. > > So what is rfkilld suppose to be doing when receiving this report? What > is the expected behavior? Why do we bother with multi-OS crap here? I am > really unclear what are we trying to solve here. Well, apparently people want to use the BIOS to store the current rfkill state -- this lets them do that. Now, I don't care if you implement it or not, but now they could. The point really is that when rfkilld starts up it has to impose a policy, and the question is what that policy is and where it is stored, if desired, across shutdowns. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
