88E1111 LINUX DRIVER DOWNLOAD
|Date Added:||16 November 2016|
|File Size:||15.33 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Please upgrade to a Xilinx. We changed our HW definition to make that a GPIO, and we take it out of reset in llinux early board init function of u-boot. Yes, I have tried it, but eth1 still doesn’t work. We are glad that we were able to resolve this issue, and will now proceed to close this thread.
net/phy: Fix copper/fiber auto-selection for 88e1111 [Linux 2.6.27]
I’m looking for some insight that I’m missing, or some other clue to indicate why the kernel drivers can’t detect PHY1 at address 1 correctly. All times are GMT Now from the Liux board at the u-boot prompt, I can ping other computers successfully and load the kernel. Note that I am using two different sub-nets – the BB code is On.
I’m just using the following default enviroment parameters: The device tree in the newer kernels uses the MACB drivers. Not sure about the dsa or link. All forum topics Previous Topic Next Topic. Click Here to receive this Complete Guide absolutely free.
The Ubuntu kernel developer has said that the vendor sk98lin will be placed in the kernel package for Breezy which should solve all the problems ljnux above and below.
According to a Xilinx FAE: I have verified that I can read the OUI bits from the PHY registers using u-boot mdio read 0 2, mdio read 1 2 – other addresses do not respond. This kernel will have the sk98lin module ready to go which hotplug will find and load. July 13th, 6.
Marvell 88E PHY ethernet controler. So I would suggest you to try testing the setup in Reluctant to pursue it as we are not using Petalinux:. Finally, I saw this thread for Petalinux, which I was not able to locate the patch for, but it seems related.
We have detected your current browser version is not the latest one. Hi, We have the same problem here. However, I don’t see an error in my boot log, and in fact it assigns the PHY id correctly to eth0 and 881111 It’s almost as if the default config of the PHY is enough to pass data to the eth1 interface even though it hasn’t been configured.
Marvell 88E Reset Sequence – Vlad Lazarenko
What other kernel settings did you have to enable to allow the Marvell 88e PHY to have the correct drivers from petalinux? On my board, the ping fails.
An update on this issue. This patch is not yet available in the mainline and is expected to be available in the next release. Content on this site may contain or be subject to specific guidelines or limitations on use. The environment and serial console appear to be configured properly, BUT my Ethernet interface is not working yet. Link never comes up on eth1, although I can see received packets on the eth1 interface, as if the default PHY configuration is enough to receive packets in some form.