>> > See the discussion between Henrique and me >> > "[RFC] b43: A patch for control of the radio LED using rfkill" >> > from last week. So I read that thread and first conclusion I came to is that the whole long thread was there due to fact that you were not able to define rfkill in the same language even though Henrique spent a lot of time on documentation. iwlwifi HW is more like b43 has ability for hard and soft killing the radio physically. So what we define as soft rfkill is actually writing the register to the HW and that was my intention when I'm talking about soft rfkill. I don't define rfkill to be singal from input device. I guess that the confusion about connecting hw switch to rfkill line comes from difference between USB and PCI devices. While Wifi PCI usually sits in a mini card slots witch defines rfkill line by spec this is not the case in a USB dongle so this have to delivered around, this is rather deficiency in USB spec. Of course USB can sit also in mini card but that's not general case. Soft rfkill line in PCI devices is here to answer needs such as txpower off/on so this is not the same think as catching external event of hw switch and applying rfkill into devices or other tricks that laptops vendors do to implement it. When I'm talking about policy this is decision how radio state is drawn from sort and hw rfkill switches in PCI context. I have to read some more about your conclusions in the thread so I won't continue here I hope Emmanuel and I will come to some implementations soon as we need to close the rfkill bugs in iwlwifi that comes from fact that mac80211 is not in the game yet. (again rfkill in register level). Thanks Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
