[U-Boot-Users] U-boot automatic selection of redundant ethern et interfaces?
mdoherty at arca-technologies.com
Wed Oct 29 10:20:48 CET 2003
Thanks for your reply enzo,
as it happens I'm quite happy with the functionality I have now, though I'll
certainly have a good sift through your driver :)
From: Figini Enzo
To: 'Mark Doherty'
Cc: u-boot-users at lists.sourceforge.net
Sent: 29/10/03 07:33
Subject: R: [U-Boot-Users] U-boot automatic selection of redundant ethern et
> -----Messaggio originale-----
> Da: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net]Per conto di Mark
> Inviato: martedì 28 ottobre 2003 14.01
> A: 'Wolfgang Denk'
> Cc: 'u-boot-users at lists.sourceforge.net'
> Oggetto: RE: [U-Boot-Users] U-boot automatic selection of redundant
> ethern et interfaces?
> Dear Wolfgang,
> > I don't know if the "ping" code takes redundand ethernet
> > into account, i. e. if it will toggle interfaces. I don't
> even know
> > if this makes sense - "ping" is intended to test if
> somebody is
> > responding, and it makes probably no sense here to
> > between the remote ost being down or cable disconnected or
> > broken.
> > It's a differetn issue with a network boot (dhcp, bootp
> or tftp
> > command) - you expect these to work, and if they are
> failingit seems
> > a good idea to try an alternative inteface if there is one.
> It works as you suggested, ping doesn't use redundant
> interfaces but tftp
> certainly does, initially it times out the first time it
> tries a transfer
> (which initially threw me!) but the second time it works
> nicely. Exactly
> what I was looking for,
> thank you.
I had the same problem in our propritary board based on MPC8260.
I modified the fcc driver files for use the fcc like external driver
new define and work fine (also with tftp).
If it's what you need, see attached file.
More information about the U-Boot