jcdutton

The lynxi is selected. But no link is established.

The attached patch fixes the SFP for me. [sfp-fix1.diff.txt](https://github.com/frank-w/BPI-Router-Linux/files/14813329/sfp-fix1.diff.txt)

I don't think my transceiver uses a realtek phy. What command do I use to identify the phy?

The SFP transceiver presents I2C interface on 0x50, 0x51, 0x56. So, it looks to me that it supports multiple different protocols over I2C. For example, 0x51 has this: CNS8TUTAAC30-1410-04V04 and...

``` i2cdump -y 0 0x56 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 10...

I tried with the rollball and I added some debug. It comes back saying rollball not found.

@frank-w Apparently the 0x4f51ea19 is a motorcomm YT8821 PHY.

Yes, I did delete it. It did not actually work. I am working on a different patch. Just trying to work out where exactly the *2 needs to happen in...

Well, on the positive side, I have the yt8821 phy working using C22. Notice the added "

In C22 mode, the motorcomm yt8821 phy is setting link up in phydev->link = 1. I have not yet found out how to propagate that to the ethtool "Link detected"...