If they both operate at 2. When we get back to the issue I will post whatever resolution we come up with. On my system that causes a hang which I could not get out of. 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. No license, either express or implied, by estoppel or otherwise, is granted by TI. So you may be in the same situation as me I’ll update you when I have more information.
|Date Added:||9 May 2015|
|File Size:||59.82 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
July 13th, 7.
net/phy: Fix copper/fiber auto-selection for 88e1111 [Linux 2.6.27]
Patch is applicable ONLY to the Introduction to Linux – A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. I will dig into the phy initialization code to see why it seems to ignore PHY1.
Linux Kernel Thanks Panou. Have you tried with slightly rearranged device tree like this? I had seen that, but we run both PHYs a 1. Liinux you need to reset your password, click here. Mentions Tags More Cancel. Click Here to receive this Complete Guide absolutely free. Join our community today! I am running 32bit ubuntu Hoary 5. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.
Do you have another question? Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Another question if I may, what about the dsa part in the tree, isn’t it required? The device tree in the newer kernels uses the MACB drivers. 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. Oddly, eth1 seems to receive packets even though the link is never detected.
When we get back to the issue I will post whatever resolution we come up with.
Marvell 88E Reset Sequence – Vlad Lazarenko
Sep 30, 9: Due to the holidays, responses may be delayed. TI and its respective suppliers and providers of content make no representations linhx the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right.
Please visit this page to clear all LQ-related cookies. Content on this site may contain or be subject to specific guidelines or limitations on use. I suspect this is a software issue.
This patch is not yet available in the mainline and is expected linuux be available in the next release. FYI, the patch is here, but not applicable to any of the current Xilinx kernel releases: Thanks for the information. 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.