From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Warren Date: Thu, 30 Apr 2009 14:32:59 -0700 Subject: [U-Boot] Disable features In-Reply-To: <49FA1674.9020109@siconix.com> References: <49FA0922.2000107@siconix.com> <20090430205506.4B62F83420E8@gemini.denx.de> <49FA1279.5080406@siconix.com> <20090430211504.A18F183420E8@gemini.denx.de> <49FA1674.9020109@siconix.com> Message-ID: <49FA190B.8050500@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Derek Ou wrote: > Wolfgang Denk wrote: > >> Dear Derek Ou, >> >> In message <49FA1279.5080406@siconix.com> you wrote: >> >> >>> When we have the Network support compiled, it takes a few second to do >>> the auto-negotiation >>> >>> >> That should be part of the network init sequence, which should only be >> run when you run a network command. >> >> > The board goes to auto-negotiation before boot delay count down. So > it's before I can run > any command. I will look into the network init routine then. > >>> even though MAC chip is not on board. Then it fails out and goes to >>> autoboot. Is it a board specific problem or system problem? >>> >>> >> Board (or architecture) problem. >> Which board / architecture is this? >> >> > It's an Atmel AT91SAM9263(ek) board. ARM architecture. > >> Best regards, >> Wolfgang Denk >> >> Do you have CONFIG_RESET_PHY_R defined? It forces a call to eth_init(), which most likely causes the delay you're seeing. Try commenting it out in your config file. regards, Ben