From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1at96F-0003Q3-HF for barebox@lists.infradead.org; Thu, 21 Apr 2016 07:32:33 +0000 Date: Thu, 21 Apr 2016 09:32:06 +0200 From: Sascha Hauer Message-ID: <20160421073206.GC21638@pengutronix.de> References: <20160419071110.GO9102@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: Fwd: Micrel KSZ9031RN PHY problem To: Guillermo Rodriguez Garcia Cc: barebox@lists.infradead.org, Philipp Zabel On Wed, Apr 20, 2016 at 05:58:40PM +0200, Guillermo Rodriguez Garcia wrote: > Hello, > > 2016-04-19 9:11 GMT+02:00 Sascha Hauer : > > Hi Guillermo, > > > > +Cc Philipp Zabel who ported the patch to barebox > > > > On Mon, Apr 18, 2016 at 04:49:47PM +0200, Guillermo Rodriguez Garcia wrote: > >> Hello all, > >> > >> I am playing with barebox on an Atmel SAMA5D3 Xplained board. It is > >> now working fine for the most part, however after updating to the > >> latest sources from git I found a problem that I had not seen before. > >> > >> This board has two Ethernet interfaces; eth0 uses a Micrel KSZ9031RN > >> PHY, and eth1 uses a Micrel KSZ8081RNB PHY. > >> > >> It seems that after release 2016.03.0, eth0 does not work anymore with > >> some routers. Specifically I found this problem with a Comtrend > >> VG-8050. I have tested other routers and the problem was not present > >> there. > >> > >> After some research it seems that the problem is caused by this > >> commit: http://git.pengutronix.de/?p=barebox.git;a=commit;h=da89ee8f2e04e116410632a185024f58b8262d87 > >> > >> Before this commit eth0 was working fine. After this commit, the link > >> cannot established anymore: > >> > >> [...] > >> barebox:/# ping 192.168.0.128 > >> ping failed: Network is down > >> > >> Before diving further into this I thought it could be a good idea to > >> ask, in case someone can shed some light here. > > > > I have no idea what the issue is here. We might have to make this option > > configurable via devicetree to give boards different options. Since the > > patch comes from the Linux Kernel, do you have the same problems under > > Linux? > > I'm trying to get the latest kernel to boot. The latest version > supported by Atmel is 4.1, which doesn't have the patch yet. Will > report back asap. Thanks. We can revert this patch since Philipp only ported it to stay in sync with the kernel. Anyway, if it makes problems we'll probably need a solution for the kernel aswell. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox