David Lyon wrote:
It's interesting that I2C is a actually a multi-master master/slave system.
So there doesn't appear any theoretical reason as to why it wouldn't work.
The lack of two I2C ports on the RPi would be a practical reason. The sense
of master and slave carries electrical
On Wed, Jun 5, 2013 at 9:39 AM, Glen Turner g...@gdt.id.au wrote:
The lack of two I2C ports on the RPi would be a practical reason. The sense
of master and slave carries electrical implications, so a port can't change
from one to the other without restarting the bus and all of its devices.
On Sat, Jun 1, 2013 at 5:30 PM, Chris Barnes chris.p.bar...@gmail.comwrote:
This one might be impossible but does anyone have any clues for running
TCP/IP over the I2C bus?
I have a few Raspberry PIs and I'd like to create an Out Of Band network on
them by linking them all by I2C and then
Wouldn't Modbus be a more suitable framework for out-of-band management?
It's normally used over RS-485 networks - a single pair multi-drop
configuration with a single master. It would have far lower overhead than
TCP/IP. You might start at www.modbus.org/tech.php
.
Cheers,
Kevin.
On 4 June
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 name
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 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
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
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 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
This one might be impossible but does anyone have any clues for running
TCP/IP over the I2C bus?
I have a few Raspberry PIs and I'd like to create an Out Of Band network on
them by linking them all by I2C and then running TCP/IP over it.
Any suggestions?
--
Kind Regards,
Christopher Barnes
On Sat, Jun 1, 2013 at 5:30 PM, Chris Barnes chris.p.bar...@gmail.comwrote:
This one might be impossible but does anyone have any clues for running
TCP/IP over the I2C bus?
I have a few Raspberry PIs and I'd like to create an Out Of Band network on
them by linking them all by I2C and then
Here's the link to that project:
- http://usbip.sourceforge.net/
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
On Sat, Jun 1, 2013 at 5:42 PM, David Lyon
david.lyon.preissh...@gmail.comwrote:
It's probably much easier to just use the network port that's already
available on the Raspberry-Pi.
or maybe rs232, then you can use ppp.
You could buy a hub/switch and some RJ45 cable and it would be done
Question 0 is do you really need tcp/ip?
If you did I'd be looking to see if you can bind an i2c endpoint to a
serial port then running some sort of ppp server on it.
On 01/06/13 17:30, Chris Barnes wrote:
This one might be impossible but does anyone have any clues for running
TCP/IP over
hmm, probably dont NEED tcp/ip. would be handy though. I just thought if
someone has built an implementation i'd be keen to make use of it.
On Sat, Jun 1, 2013 at 11:11 PM, Jake Anderson ya...@vapourforge.comwrote:
Question 0 is do you really need tcp/ip?
If you did I'd be looking to see if
The only issue that I can see is that I2C is a bus/master protocol. I know
the Linux drivers support being the Master but I'don't know if it supports
being a slave.
So I'm not even sure if you could easily accomplish it without using extra
hardware such as PIC/AVRs.
On 01/06/2013 11:11 PM, Jake
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 requests, netbios name requests, etc. Otherwise the slaves
18 matches
Mail list logo
