From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Peverley Date: Tue, 04 May 2004 13:32:37 +0100 Subject: [U-Boot-Users] [PATCH] lan91c96 driver MAC address detection In-Reply-To: <20040504120615.F1117C109F@atlas.denx.de> References: <20040504120615.F1117C109F@atlas.denx.de> Message-ID: <40978D65.7030805@mpc-data.co.uk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > The rules are simple and documented: Sure, I've read these... > You cannot use BOOTP (nor ony other network related protocol) to > detect a MAC address!!! I think that either we operate on utterly different brainwave-lengths or theres some kind of language barrier issue here! If you issue a 'bootp' command to u-boot via its interface as I stated, the following call sequence happens if you're using the lan91c96 (with patch) or smc91111 ethernet devices : do_bootp() [cmd_net.c] netboot_common() [cmd_net.c] NetLoop() [net.c] eth_init() [lan91c96.c] smc_open() [lan91c96.c] smc_get_ethaddr() [lan91c96.c] get_rom_mac() [lan91c96.c] So in practical use, issuing a bootp detects the mac address of the adapter. > (nor ony other network related protocol) Well, the following network related protocol calls : do_tftpb() do_rarpb() do_dhcp() do_nfs() all call netboot_common() so will in effect detect the MAC address as well ;-) Best Wishes, Dave Peverley --------------------------------------------------------------------------- Dave Peverley, Software Engineer, MPC Data Limited. Phone : [+44] (0) 1225 868 228 Web : http://www.mpc-data.co.uk