On Fri, Aug 27, 2010 at 08:58:42AM -0700, Johannes Berg wrote: > On Fri, 2010-08-27 at 08:55 -0700, Luis R. Rodriguez wrote: > > On Fri, Aug 27, 2010 at 8:51 AM, Johannes Berg > > <johannes@xxxxxxxxxxxxxxxx> wrote: > > > On Fri, 2010-08-27 at 08:48 -0700, Luis R. Rodriguez wrote: > > > > > >> > Well, there's no way we can reliably wake up exactly before a beacon by > > >> > implementing that in software, hard real-time hasn't been achieved in > > >> > Linux yet :-) > > >> > > >> Keyword here is *exactly*. I don't want to wake up *exactly* at DTIM, > > >> only ensure we don't sleep during it and the send buffered frames and > > >> multicast traffic data. Why can we not implement this on mac80211? > > > > > > Well, how long before the beacon do you want to wake up to catch it? > > > 1ms? 10ms? 100ms? 1000ms? What if the system is busy? > > > > I cannot say what would work best, how about half a beacon interval early? > > Why are we even discussing this anyway? It doesn't matter for a power > save implementation since you better offload it to the device so you get > as exact timing as you can? ath9k hardware does not have a CPU to offload this. I just noticed we do however already wait for the dtim count to go to 0 and also all RX'd buffered data through ath_rx_ps() but even if then it seems we need and API to enable drivers to flag when they want to disallow scanning (dynamic power save can be disabled already by the driver at will I think). Otherwise we would have to use something like the patch I'm going to send, which is fine for now. Luis -- 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
