I'm catching up with my u-boot list emails, so please forgive my late reply here:
On 2/14/07, Ben Warren bwarren@qstreams.com wrote:
The purpose of this configuration option (CONFIG_NET_MULTI) is to automatically cycle through the available Ethernet devices when attempting a network connection, moving on when a device's link is down.
This is such an arcane purpose - I wonder how many people think this is a valuable feature? In most cases a system has multiple ethernet interfaces, those interfaces are connected to different subnets, and quite often it is meaningless to try communicating with a host A on interface B. This automated interface skipping is actually a very harmful in some situations.
The ability to register multiple interfaces and pick one of them for all communications is a great one. But the automated switch from interface to interface should definitely not be the default behavior.
I wonder what is the u-boot community consensus on this issue. I guess not many people bring up boards with multiple enet interfaces...
cheers, vadim
I imagine the person who wrote the tsec didn't imagine the case where someone would only want to use one device.
I intend to clean up the eth.c file some time soon because as you can see it's a big mess of #ifdefs.
Enabling CONFIG_NET_MULTI shouldn't cause you any problems. Just go ahead and do that, but only define the appropriate CONFIG_MPC85XX_TSEC? flags.
If this isn't clear, just let me know.
regards, Ben
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users