From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-vk0-x22b.google.com ([2607:f8b0:400c:c05::22b]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1asuWs-00061S-DR for barebox@lists.infradead.org; Wed, 20 Apr 2016 15:59:03 +0000 Received: by mail-vk0-x22b.google.com with SMTP id n67so56391654vkf.3 for ; Wed, 20 Apr 2016 08:58:41 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20160419071110.GO9102@pengutronix.de> References: <20160419071110.GO9102@pengutronix.de> Date: Wed, 20 Apr 2016 17:58:40 +0200 Message-ID: From: Guillermo Rodriguez Garcia 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: Sascha Hauer Cc: barebox@lists.infradead.org, Philipp Zabel 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. -- Guillermo Rodriguez Garcia guille.rodriguez@gmail.com _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox