On Thu, Feb 9, 2012 at 7:33 PM, Sridhar Dhanapalan <[email protected]> wrote: >> Looking for the happy middle ground that doesn't interfere with >> collaboration. > > Emphasis on collaboration stability, but we would prefer not to have > massive battery drain while doing so. We understand that there are > trade-offs.
I think its hard to find a middle ground at the moment. Maybe it is just subjective. As John Gilmore points out, we have years of experience of applying workarounds and it hasn't brought brilliant results. Recent workarounds have already shifted us quite significantly to the stability side (sacrificing power savings) - waking up on all multicast frames, apparently even ones that wouldn't normally be sent from the hardware to the driver - but we are still left with a (IMO) substandard experience for the field. If you apply the collaboration workaround in question you just shift the problem to other areas, such as presence and web browsing. In terms of the real solution, we are making progress on some of the issues. Slowly but surely. Daniel _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
