On Thu, 2006-08-24 at 18:26 -0700, Dan Brown wrote:
> The issue with that is that I will be using other modules, so need a
> different solution than ethernet...
> Was thinking more along the lines of a serial or maybe parrellel
> solution, maybe using the gpio's...
Seems like if you can scrounge up 4 GPIO pins,you can bit bang data out
a GPIO pin pretty easily. You just need to build interrupt drivers for
each GPIO pin. You need a bi-directional data pin, a clock pin, a
receive enable pin, and a strobe pin. Load up a register with data,
then clock out each bit in the register (your clock pin bounces once for
each bit), then bounce your strobe pin at the end. your rx stix would
then fill a rx register and when he sees the strobe pin bounce, he knows
he's done. You could then place these on a bus and develop some kind of
rs-485ey adressing scheme. =20
But that sounds like a pain. I have a card that I just stuck a 485
transciever on one of my uarts and can communicate to all kinds of stuff
> ----- Original Message ----
> From: ken staton <ken.staton@...>
> To: General mailing list for gumstix users.
> Sent: Thursday, August 24, 2006 7:44:04 PM
> Subject: Re: [Gumstix-users] Multiple Gumstix Communications
> Hi Dan,
> If you've just connecting two use a cross over cable.
> In fact with netduoMMC's and cross over cables you
> can connect as many gumstix as you want.
> On 8/24/06, Dan Brown <dan@...> wrote:
> > What would be the most reliable/stable methodof having multiple
> Gumstix talk
> > to each other?
> > I'd like to dedicate one of them to managing filesystems and then
> have one
> > handling other tasks... The filesystem GS will need to export the
> > filesystems (ie: NFS) to the other gumstix.
> > I'd prefer NOT to use ethernet. (Switches/hubs are just too big and
> > hungry...)
> > Suggestions here are welcome!