From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mathieu Deschamps <mathieu.deschamps@com2gether.net>
Date: Mon, 27 Mar 2006 10:01:51 +0200
Subject: [U-Boot-Users] Valid EMAC address
Message-ID: <200603271001.51241.mathieu.deschamps@com2gether.net>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hello ,

I've just found that an invalid EMAC address -I guess-  I've given to test,  
was the reason for all NET_COMMANDS (ping, tftpboot and the like) to gently 
fail without any errors whereas NET_DEBUG and ET_DEBUG were definied.

Indeed, I've change supposed invalid addr 47:55:47:55:47:55:aa to
12:43:56:78:90:aa and it worked. So here I come and apolozige in advance
if somebody already answered theses, I haven't found anything relevant in
archives  :

How to determin if a EMAC is valid/legal ? Why u-boot doesn't implement 
such a validiy test -at least when debugging is defined- in order to defeat 
that strange developper reflex, looking for _the_ inexisting bug ?



Best Regards,
 
Mathieu Deschamps

--
Com2gether Design Center
Electronic and Embedded Engineering Services
www.com2gether.net