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 can only send data in response to a request from the master.
oh well, never mind. On Sun, Jun 2, 2013 at 9:51 AM, David Lyon <[email protected]>wrote: > 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 Anderson" <[email protected]> wrote: > >> 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 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? >>> >>> >>> >> -- >> SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ >> Subscription info and FAQs: >> http://slug.org.au/faq/**mailinglists.html<http://slug.org.au/faq/mailinglists.html> >> > -- Kind Regards, Christopher Barnes e. [email protected] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
