Hi Helmut, On Thu, 2009-03-26 at 23:25 -0700, Helmut Schaa wrote: > Hi, > > Am Freitag, 27. März 2009 schrieb reinette chatre: > > On Thu, 2009-03-26 at 13:58 -0700, Helmut Schaa wrote: > > > Assume the following situation: > > > > > > You only have one killswitch for both, wireless and bluetooth. The wireless > > > interface is down because it is unused and the user wants to use bluetooth > > > and enables it via the killswitch which also means that wireless gets > > > unkilled. Now restarting the adapter needs more power then keeping the > > > adapter down. In short: if the interface is down the user (space) does not > > > want to use the interface and probably wants to save power as well. > > > > Your measurements are very fine grained :) Will this be measureable? > > Heh, you know the internals of the devive ;) but I guess waking up the > adapter (and thus starting the firmware) even if the interface is unused > will surely need more power than not doing so. If interface is down then mac will not ask us to start the interface in the first place. If interface is up and mac asks us to start interface then the driver will do so. In this case, if rfkill is enabled, then the driver will not do much ... definitely not load firmware and thus start using up power. Only when the user changes rfkill state will we actually get the firmware going. Reinette -- 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
