Hi Matthew, > > > you know that we re-wrote RFKILL completely. You can kill a Bluetooth > > > device from within the kernel. And this looks like a hardkill of the > > > Bluetooth interface. > > > > > > > > That's pretty similar to what I was trying to accomplish with the > > original patch that started all of this discussion. I'll attach that > > original patch so you can see what I'm talking about. > > I disliked this for a couple of reasons. The first is that it forces an > rfkill even on hardware that doens't have this behaviour. The second is > that it's working around a quirk on hardware that this driver really > isn't reponsible for. I don't agree with how the patch is done, but in theory it is what RFKILL is all about (after the re-write). However it has to be hardkill and not a softkill. The softkill is a userspace decision while the hardkill comes from actually hardware or firmware in this case. Seems the Dell hardware/firmware is kinda stupid and inconsistent here and I have no problem solution. However adding a special HID driver with this quirk might be better anyway. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
