From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Wed, 04 Mar 2015 22:31:34 +0100 Subject: [PATCH] ARM: i.MX6Q: Add fixup for RTL8211E Gigabit Ethernet PHY In-Reply-To: <5019881425501158@web17m.yandex.ru> References: <1425404579-30591-1-git-send-email-rockford@yandex.ru> <5019881425501158@web17m.yandex.ru> Message-ID: <2318103.drIWJFctaK@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wednesday 04 March 2015 23:32:38 ????? ?????? wrote: > 04.03.2015, 23:18, "Fabio Estevam" : > > On Wed, Mar 4, 2015 at 5:05 PM, ????? ?????? wrote: > >> Actually, I don't know. I've discovered this when I wanted to boot a more recent kernel > >> on this board, and network wasn't working. So I've had to disassembly a vendor's binary only module > >> to discover how they handle this situation. > > > > Do you use the generic PHY driver or do you have CONFIG_REALTEK_PHY enabled? > > CONFIG_REALTEK_PHY=y > CONFIG_FIXED_PHY=y > > > In case you use the realtek PHY driver and still see the issue, can't > > you fix this in drivers/net/phy/realtek.c instead? > > I think there it will require a more work with board detection than here and will > populate a driver with unnecessary for most users code. But you said earlier that it's board independent and a property of the SoC instead. Can't the ethernet driver call phy_start_aneg() for the same effect, like a lot of other ethernet drivers do? Arnd