On Mon, 2009-06-01 at 09:28 -0300, Henrique de Moraes Holschuh wrote: > It can have default values just fine. And you can't wait for userspace or > platform drivers to register a default, it just doesn't work, you cannot > expect that all relevant drivers are loaded before "rfkilld". > > Just don't expose a rfkill type until the first rfkill structure of that > type gets registered. THAT closes all holes in a sensible, > principle-of-least-suprise way. The current code (including the rewrite) > already deals with defaults and firmware-backed state storage just fine in > that case. All you need is a full interface that deals with global state > hotplug (which ain't difficult, that's one or two more notifications only). Global state hotplug is just not really possible to support, and I don't think even your original code supported that, since it cannot affect previously registered rfkill instances. You definitely don't want to hotplug a wireless device and turn off all others "due to that". johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
