I am sure we don't want a scenario where the user will have no chance whatsoever to connect to a salut network. Right?
On Feb 19, 2008 12:02 PM, John Watlington <[EMAIL PROTECTED]> wrote: > > We ALWAYS have multicast traffic. Blindly waking on each > received multicast packet will ensure that we only sleep for > milliseconds. > > wad > > On Feb 19, 2008, at 9:13 AM, Chris Ball wrote: > > > Hi, > > > >> It does feel like we should turn off suspend for some of our > >> testing. I've experienced similar problems. > > > >> Chris, do you recommend removing ohm? Or is there something else we > >> should try? > > > > I recommend fixing the bug. :) We know that we intend to have the > > CPU > > turned off most of the time on our laptops on the mesh -- why is the > > presence service incompatible with this? Should we be setting the > > wireless module to wake on multicast, so that we can respond to > > whatever > > traffic the presence service is using to see who's online? Should > > it be > > using unicast traffic instead? What is it in Avahi's code path that > > causes its peer list to be emptied on resume? > > > > If we have to disable OHM to test something in particular, that's > > okay, > > but we won't be testing what we plan on shipping if we do so. > > > > Thanks, > > > > - Chris. > > -- > > Chris Ball <[EMAIL PROTECTED]> > > _______________________________________________ > > Devel mailing list > > [email protected] > > http://lists.laptop.org/listinfo/devel > >
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
