On Sun, 2009-07-19 at 15:14 -0500, Peter Tyser wrote: > On Wed, 2009-02-04 at 15:14 -0600, Peter Tyser wrote: > > Previously, waiting for auto-negotiation would only occur if a valid > > link had been detected. Problems arose when attempting to use a > > tsec immediately after bootup but before link was achieved, eg: > > => dhcp > > Auto-neg error, defaulting to 10BT/HD > > eTSEC1: No link. > > Auto-neg error, defaulting to 10BT/HD > > eTSEC2: No link. > > => > > > > With this patch applied the same operation as above resulted in: > > => dhcp > > Waiting for PHY auto negotiation to complete. done > > Enet starting in 1000BT/FD > > Speed: 1000, full duplex > > > > Signed-off-by: Peter Tyser <pty...@xes-inc.com> > > This patch originally spawned a lot of discussion but nothing came of > it. Could we get it applied? If not, what do I need to do to get a > similar change in? > > Right now if you have autoboot enabled that uses network operation, you > have to add an arbitrary delay to the boot process to give > autonegotiation time to complete, which is annoying. The negotiation > time varies depending on switch too, so the delay can never be exact.
Ping... _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
