On Wed, Feb 8, 2012 at 10:59 PM, James Cameron qu...@laptop.org wrote:
No, that's not how ad-hoc works. I'll simplify and translate for you.
Your explanation is correct but doesn't exactly match the buggy
behaviour of our wireless hardware/firmware. As far as I can tell, the
ad-hoc nodes in our
On Wed, Feb 08, 2012 at 10:16:53PM +1100, Sridhar Dhanapalan wrote:
Ad-hoc connections only scale to a limited number of participants
before problems begin to occur.
What are the problems you observe? It may be that the problems you
observe are not due to the ad-hoc network, but due to
On Thu, Feb 09, 2012 at 03:11:42PM +1100, Sridhar Dhanapalan wrote:
Hmm I am thinking that my understanding of the ad-hoc implementation
might be incorrect.
I was under the assumption that one XO acts as the ad-hoc host, and
the others connect to it. That made me wonder whether that host
To expand on James' excellent notes...
On Wed, Feb 8, 2012 at 11:59 PM, James Cameron qu...@laptop.org wrote:
The beacon is used for timing the transmissions, so that they occur in
And that is _all_ it can do. It just broadcasts a beacon, like a
metronome for a band recording in a studio.