From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Mack Date: Wed, 22 Apr 2009 20:08:11 +0200 Subject: [U-Boot] Enabling smc911x driver In-Reply-To: <5e088bd90904221031x31c423aar2ebf98a2a6aa687d@mail.gmail.com> References: <5e088bd90904210811j2bf9fe7ep922fb1564389445e@mail.gmail.com> <49EDF526.9060709@gmail.com> <5e088bd90904220752o5e77e6adn2f69cac6f4d3db22@mail.gmail.com> <20090422155144.GA19863@buzzloop.caiaq.de> <20090422155443.GB19863@buzzloop.caiaq.de> <5e088bd90904221031x31c423aar2ebf98a2a6aa687d@mail.gmail.com> Message-ID: <20090422180811.GA18618@buzzloop.caiaq.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Apr 22, 2009 at 10:31:52AM -0700, Steve Sakoman wrote: > >> How did you set this MAC address? Does the hardware read it from a > >> connected EEPROM or did you manually set it in your environment. > > It is manually set in the environment since the prototype hardware > doesn't have the eeprom. Assuming you're going to boot Linux on that board, you will face the next problem that U-Boot will reset the controller before the kernel boots and thus vanishes the MAC address from the chip. I sent in another patch for that which contionally disables this reset so that the Linux driver can actually read the address again and use it (with the SMSC911X_SAVE_MAC_ADDRESS flag set). But as Mike Frysinger pointed out, this is not the intended way to go as the MAC is only programmed if U-Boot ever performed any network transaction. So there is need for some other approach, just wanted to let you know. Daniel