On 4 April 2011 11:23, Jonas Gorski <jonas.gorski+open...@gmail.com> wrote: > Both RTL8366x PHY drivers use the same PHY ID, so both match for either > chip, which results in the following behavior when using a RTL8366RB with > Port 4 as separate WAN port (seen on a WZR-HP-G301NH): > > - rtl8366rb probes addr 4 > - rtl8366s phy driver matches phy id => attaches > ... > - rtl8366s_phy_config_init gets called and fails (since wrong MII bus) > - eth1 is unsable
Looking further at the code I start to wonder whether the special PHY drivers are actually necessary. The only real difference from the generic phy driver is the nop config init (and the MII bus check); everything else is using the generic implementations. Also the phy driver only attaches to the wan port phy, so there is no need for any switch pseudo phy handling. This really leaves the config init, and the generic phy driver's config init just reads out the features from the mii registers, so this should probably work fine, too (okay, it's realtek, but still ;). Regards Jonas _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
