On 04.04.2016 15:58, Andrew Lunn wrote:
On Mon, Apr 04, 2016 at 03:50:02PM +0200, Petr Kulhavy wrote:
Hi Andrew,
thanks a lot for the link. In the meantime I've understood the issue
better. It is due to the fact that the PHY is pin-strapped to
address 1 and broadcast (at address 0) is enable
On Mon, Apr 04, 2016 at 03:50:02PM +0200, Petr Kulhavy wrote:
>
>
> On 04.04.2016 14:31, Andrew Lunn wrote:
> >Hi Petr
> >
> >You might want to take a look at:
> >
> >http://lxr.free-electrons.com/source/drivers/net/ethernet/ti/davinci_mdio.c#L137
> >
> >It seems to be asking the hardware about t
On 04.04.2016 14:31, Andrew Lunn wrote:
Hi Petr
You might want to take a look at:
http://lxr.free-electrons.com/source/drivers/net/ethernet/ti/davinci_mdio.c#L137
It seems to be asking the hardware about the phy mask.
Andrew
Hi Andrew,
thanks a lot for the link. In the meantime I'
On Mon, Apr 04, 2016 at 10:18:30AM +0200, Petr Kulhavy wrote:
> Hi,
>
> I'm experiencing a peculiar problem with PHY communication in the
> current davinci-mdio.c driver.
> After upgrading from kernel 3.17 to 4.5 my DT based AM1808 board
> started having issues with the PHY communication.
> The MA
Hi,
I'm experiencing a peculiar problem with PHY communication in the
current davinci-mdio.c driver.
After upgrading from kernel 3.17 to 4.5 my DT based AM1808 board started
having issues with the PHY communication.
The MAC is detected, the MDIO is detected, the PHY is detected
(twice?!?!), ho
Hi,
I'm experiencing a peculiar problem with PHY communication in the
current davinci-mdio.c driver.
After upgrading from kernel 3.17 to 4.5 my DT based AM1808 board started
having issues with the PHY communication.
The MAC is detected, the MDIO is detected, the PHY is detected
(twice?!?!), ho
