I enable eth0 and see transactions on the MDIO bus. I will post when I get the new release and test it. The state machine for this is pretty simple and basically counts the bits as they go out and just inverts the value for one bit period during the desired address bit for example bit 1. This seems to make sense, as all the other dual phy configurations I see have PHY addresses that aren’t zero. Copyright c – Intel Corporation.

Uploader: Dubei
Date Added: 18 January 2004
File Size: 56.15 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 75763
Price: Free* [*Free Regsitration Required]

Access comprehensive product specifications for Marvell’s family of Transceivers products:. Again, this appears to be a software issue. Additional features of the Alaska GbE PHYs include a high-level of integration in thermally-efficient packages that optimize PCB real estate and enable fan-less heat-sink-less designs.

Yes, I have tried it, but eth1 still doesn’t work. Thu Feb 18 Marvell PHYs products can also be combined with Marvell’s switching products for a complete networking solution. To contact Marvelo Sales, please submit your inquiry via request for information below.

Alaska Gigabit Ethernet Designed to meet the demands of next generation green networks. Driver Downloads Download the latest Marvell drivers for your specific device or application. Finally, I saw this thread for Petalinux, which I mxrvell not able to locate the patch for, but it seems related.


I will post when I get the new release and test it. We verified that before trying it in the kernel.

We have a custom board with a Zynq using two Marvell 88e PHYs for dual ethernet and have not been able to get eth1 up and running on xilinx-linux eth0 works fine. FYI, Tool and Software tags: Anyone else had it work? Ethics Supplier Responsibility Environment Community. Product Brief Marbell Product Brief. Add the phy handle to the gem sections: Build the device tree blob, and copy uImage and the.

If you want to achieve great things, then we want to talk with you. 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. Note that I am using two different sub-nets – the We are not able to run our dual GEM config.

88e Stock and Price by Distributor

Do you have any further information about this question? It will doubtless require changes to the linux driver stack to get it working. I Have met the same problem, hope could get some ideas from you! I have looked at marvepl following link, and it appears that the issue of supporting two PHYs was solved in There was a little communication confusion with Xilinx.


Alaska Gigabit Ethernet PHYs Transceivers

We have detected your current browser version is not the latest one. Note that it assigns a different MAC marfell than is assinged in the device tree file.

Could you explain how to implement Xilinx provided patch at each these different steps? I had seen that, but we run both PHYs a 1. If they both operate at 3. Thanks for the advice.

It will be fixed in the ChromeFirefoxInternet Explorer 11 karvell, Safari. With the Alaska family, Marvell delivers a new class of Gigabit PHYs designed to meet the demands of next-generation green networks.