Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2015-01-26 Thread Weedy
On Jan 26, 2015 1:44 AM, "Heiner Kallweit" wrote: > If it worked with a previous version of the driver then you could use "git bisect" to find out which change actually introduced > the problem. https://dev.openwrt.org/changeset/43332 This was the change, there was a huge fit about it at the time

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2015-01-25 Thread Heiner Kallweit
"I can plug an old 100mbit laptop into it and also have it not show up." You connect the laptop with the router or the modem? Does it work if you boot with the modem unplugged in and plug it in later? If it worked with a previous version of the driver then you could use "git bisect" to find out w

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2015-01-25 Thread Weedy
On Jan 25, 2015 1:06 PM, "Heiner Kallweit" wrote: > > To me it doesn't look like an issue with the AR8216 driver. All related output is ok. > The hardware is quite common and in case of a driver issue I would expect much more > people to complain. > > What looks a little strange to me is that ther

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2015-01-25 Thread Heiner Kallweit
To me it doesn't look like an issue with the AR8216 driver. All related output is ok. The hardware is quite common and in case of a driver issue I would expect much more people to complain. What looks a little strange to me is that there seem to be two interfaces (modem + wan) fiddling with eth

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2015-01-25 Thread Weedy
On Wed, Dec 17, 2014 at 1:48 PM, Heiner Kallweit wrote: > Ticket 18415 was closed as it was confirmed that as at least version >=43419 > is ok. > (I assume 43410 fixed the issue.) Therefore current trunk should be ok. > > However if you want to check further what the actual root cause was: > -> R

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2014-12-17 Thread Heiner Kallweit
Am 17.12.2014 um 08:47 schrieb Weedy: > > On Nov 28, 2014 3:24 PM, "Weedy" > wrote: >> >> >> On Nov 28, 2014 5:23 AM, "Heiner Kallweit" > > wrote: >> > Anybody with a 8216-based device who can test this? >> >> Me me me, me me. >> 4300 curre

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2014-12-16 Thread Weedy
On Nov 28, 2014 3:24 PM, "Weedy" wrote: > > > On Nov 28, 2014 5:23 AM, "Heiner Kallweit" wrote: > > Anybody with a 8216-based device who can test this? > > Me me me, me me. > 4300 currently running trunk with 43332 reverted. > I am at your service. Is the current trunk fixed? You never replied a

Re: [OpenWrt-Devel] ar8216: phy_init and bug report 18415

2014-11-28 Thread Weedy
On Nov 28, 2014 5:23 AM, "Heiner Kallweit" wrote: > Anybody with a 8216-based device who can test this? Me me me, me me. 4300 currently running trunk with 43332 reverted. I am at your service. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.o

[OpenWrt-Devel] ar8216: phy_init and bug report 18415

2014-11-28 Thread Heiner Kallweit
This bug report relates to a device using the AR8216 switch chip and a trunk version where the additional phy reset in 3.14 was still enabled. Seems like there was an issue with autoneg. This is not fully clear to me as after the first phy reset in the kernel phy code we do the hw_init in the driv