From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from 1.mo2.mail-out.ovh.net ([46.105.63.121] helo=mo2.mail-out.ovh.net) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1TRJNk-0005oR-5S for barebox@lists.infradead.org; Thu, 25 Oct 2012 09:05:41 +0000 Received: from mail190.ha.ovh.net (b7.ovh.net [213.186.33.57]) by mo2.mail-out.ovh.net (Postfix) with SMTP id B61F7DC2232 for ; Thu, 25 Oct 2012 11:12:31 +0200 (CEST) Date: Thu, 25 Oct 2012 11:05:33 +0200 From: Eric =?ISO-8859-1?B?QuluYXJk?= Message-ID: <20121025110533.2ae743e9@eb-e6520> In-Reply-To: <20121025084902.GO21588@game.jcrosoft.org> References: <1351101988-6681-1-git-send-email-s.hauer@pengutronix.de> <20121024183359.GN21588@game.jcrosoft.org> <20121024215649.25964bc6@eb-e6520> <20121025084902.GO21588@game.jcrosoft.org> Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH] net phy: poll for a link To: Jean-Christophe PLAGNIOL-VILLARD Cc: barebox@lists.infradead.org Le Thu, 25 Oct 2012 10:49:02 +0200, Jean-Christophe PLAGNIOL-VILLARD a =E9crit : > On 21:56 Wed 24 Oct , Eric B=E9nard wrote: > > Hi, > > = > > Le Wed, 24 Oct 2012 20:33:59 +0200, > > Jean-Christophe PLAGNIOL-VILLARD a =E9crit : > > = > > > On 20:06 Wed 24 Oct , Sascha Hauer wrote: > > > > Since we have phylib we have no instance which polls for a link. Th= is > > > > means that network boot often bails out after a powercycle or phy r= eset. > > > > This changes the link status behaviour to: > > > > = > > > > - Always check for a link if the last link test was unsuccesful > > > > - If the last check was succesful, check for a link when the last > > > > check is longer than 5 seconds ago > > > > - Try to get a link for 5 seconds. > > > 5 seconds is too long > > > = > > > and check the link is wrong you need to check the autoneg > > > the link may be down because no cable > > > = > > and the autoneg can have been successful before the cable was > > removed : how to you handle this cas ? > the advertise tell you something change > = > so you need to restart the autoneg > = so I don't really understand why you don't want to use the link information which seems to be the first thing to do before trying to launch an autoneg but why not, let see the patches when they come. Eric _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox