On Wed, Feb 2, 2011 at 1:29 PM, Johannes Stezenbach <js@xxxxxxxxx> wrote: > On Wed, Feb 02, 2011 at 07:42:51PM +0200, Kalle Valo wrote: >> So the firmware/hardware doesn't have support for tracking and waking >> up for beacons? I didn't even know that such hardware exists :) Waking >> up for beacons from host sounds very inefficient and unrealiable. All >> the devices I have seen either do this in firmware or hardware due to >> time constraints. Even at76c50x-usb, which is ancient, does all this >> in firmware. > > IMHO this is a bit exaggerated. Given that the beacon interval > is typically ~100 msecs, and typical worst cast irq latencies > on Linux 2.6 are a few 100 usecs, we can sleep e.g. 90msecs > and wake up in time to catch the beacon with high probability, thus > saving 90% on PHY power. Not perfect, but good enough, isn't it? Half-related to above, and purely from user perspective. Is there a way to disable power saving for WiFi cards globally by default (for example, by passing an option to device driver)? Having power saving turned on by default makes sense for laptops, but doesn't make much sense for desktops. And in my case (due to problem with at least some rt2xxx chips that Ivo described) it causes relatively frequent disconnects/reconnects from/to AP due to lost beacons. For my desktop system, I'd rather pass an option to device driver to have power saving default to off, and have a smoother network experience. -- 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
