On Thu, Mar 29, 2012 at 7:54 AM, Kevin Gordon kgordon...@gmail.com wrote:
In this particular use-case, in this setting, on all of the XO's, both power
saving check-boxes are turned off. The screen may dim if someone walks away
You can still close the lid, and reopen it. That triggers S/R/
You
Folks:
If one never uses mesh in a 15-20 group XO-1 classroom environment, but
always uses AP's, is there any appreciable benefit to disabling mesh
completely - perhaps to reduce chatter or power usage?
I have read one can use the following to do so, if desired:
echo 0
On Wed, 2012-03-28 at 10:17 -0400, Kevin Gordon wrote:
Folks:
If one never uses mesh in a 15-20 group XO-1 classroom environment,
but always uses AP's, is there any appreciable benefit to disabling
mesh completely - perhaps to reduce chatter or power usage?
I have read one can use the
On Fri, 2011-05-13 at 15:16 +0200, Sascha Silbe wrote:
Excerpts from Dan Williams's message of Thu May 12 05:11:36 +0200 2011:
On Wed, 2011-05-11 at 14:52 +0200, Sascha Silbe wrote:
This allows individual users and deployments to disable mesh support at
runtime, i.e. without having
Excerpts from Dan Williams's message of Thu May 12 05:11:36 +0200 2011:
On Wed, 2011-05-11 at 14:52 +0200, Sascha Silbe wrote:
This allows individual users and deployments to disable mesh support at
runtime, i.e. without having to build and maintain a custom kernel.
Does the mesh interface
On Wed, 2011-05-11 at 14:52 +0200, Sascha Silbe wrote:
This allows individual users and deployments to disable mesh support at
runtime, i.e. without having to build and maintain a custom kernel.
Does the mesh interface somehow cause problems, even when nothing is
using it? I'd expect
