On 21/04/2014 12:16, Roman Yeryomin wrote: > On 21 April 2014 12:55, John Crispin <[email protected]> wrote: >> >> >> On 21/04/2014 10:58, Roman Yeryomin wrote: >>> The target was ramips, rt2880 and rt305x subtargets at least. >>> I'm not sure how rtl8366xx differs from ip175e but both realtek >>> switch and smi parts are under drivers/net/phy/. I remember >>> when I submitted a patch to exclude realtek switch from target >>> kernel konfig and just use kernel package when it's needed by a >>> board, somebody said it will not work like this. But it did and >>> works now also. Unfortunately I don't have any hw with ip175e >>> to test... >> >> i believe you are wrong here but i will verify. to my >> understanding only smi phy drivers should work when loaded post >> ethernet init. >> >> the etehrnet driver needs the phy driver to be present when the >> of_phy_connect() is called. to my knowledge there is no mechanism >> for defeered phy attach logic. >> >> John > > grep -Hrin "rtl83" target/linux/ramips/*/config-3.10 > target/linux/ramips/rt3883/config-3.10:140:CONFIG_RTL8366_SMI=y > target/linux/ramips/rt3883/config-3.10:141:CONFIG_RTL8367B_PHY=y > target/linux/ramips/rt3883/config-3.10:142:CONFIG_RTL8367_PHY=y > > But I never touched rt3883 subtarget and I assume those lines can > be safely deleted (after including kmod-rtl836xxx package in board > profiles). >
true and should be done for sake of consistency, however somewhat unrelated to the actual topic that we are discussing _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
