On Tue, 02 Jun 2009, Marcel Holtmann wrote: > We just need to fix the platform drivers then. They should not set > global states since that is not what they are controlling. They control We should change things, yes. So that the platform stores the global state. That was half-broken on the old core (the platform stored the state of its own device, which could be out of sync with the global state), but the part of it setting the global state is correct. That needs a new in-kernel API to tie the core to platform drivers capable of storing global states without causing problems when drivers are unloaded, but it is not hard. As for NVS events, they have a clear use case: to let rfkilld know which global states it could leave alone the first time it loads, and which ones have to be restored... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
