On 03/06/2013, at 10:15 AM, Chris Barnes wrote:
> Wow thanks for that Glen.
>
> Stacks of useful info. Given me a bit more to think about.
Personally, if I were building a cluster of RPis I'd use the serial
console for remote management. The main reason for that is that crash
information gets p
Wow thanks for that Glen.
Stacks of useful info. Given me a bit more to think about.
I wasnt intending to run the PIs too far apart. At the moment i have them
in cases but i was hoping to throw them into an enclosure like a blade
system (minus the hot-swapability) or like the Pi clusters you see
On 02/06/2013, at 9:31 AM, Chris Barnes wrote:
> yeah.
>
> come to think of it. the whole master/slave process of I2C would probably
> make it terribly difficult to implement tcp/ip since each device would have
> to be able to switch from slave to master to be able to send broadcasts
> like arp
On 02/06/13 21:52, Chris Barnes wrote:
> Token ring would work.
>
> Now, i wonder if anyone has already implemented token ring over i2c
> under linux.
Just for clarity, I meant ‘token ring *type* approach’, not token ring
itself. Perhaps ‘round robin’ would have been clearer.
--
SLUG - Sydney L
Token ring would work.
Now, i wonder if anyone has already implemented token ring over i2c under
linux.
On 02/06/13 10:01, Chris Barnes wrote:
> come to think of it. the whole master/slave process of I2C would probably
> make it terribly difficult to implement tcp/ip since each device would
have
On 02/06/13 10:01, Chris Barnes wrote:
> come to think of it. the whole master/slave process of I2C would probably
> make it terribly difficult to implement tcp/ip since each device would have
> to be able to switch from slave to master to be able to send broadcasts
> like arp requests, netbios nam
