Hello, I was trying to use a port with tag/untagged vlan in a device with a RTL8367R switch (tp-link tl-wr2543nd). Part of it worked (ipv6, traffic from clients to the router, broadcast from the router) but specially "DHCP Offer" that never reached the clients. However, when I touched fib value (swconfig dev switch0 vlan 1 fib 1), all started to work. I was curious about what is the meaning of FIB=1 (or 2, 3,...7 all of them seems to make it work).
Anyway, I noticed that the driver was not a module but builtin for all the target: $ grep RTL836. target/linux/ath79/*/config* -r target/linux/ath79/generic/config-default:CONFIG_RTL8366RB_PHY=y target/linux/ath79/generic/config-default:CONFIG_RTL8366S_PHY=y target/linux/ath79/generic/config-default:CONFIG_RTL8366_SMI=y target/linux/ath79/generic/config-default:CONFIG_RTL8367_PHY=y Although it looks like just a few devices actually use it: target/linux/ath79/dts/ar7161_netgear_wndr.dtsi: compatible = "realtek,rtl8366s"; target/linux/ath79/dts/ar9132_buffalo_wzr-hp-g300nh-rb.dts: compatible = "realtek,rtl8366rb"; target/linux/ath79/dts/ar7161_dlink_dir-825-b1.dts: compatible = "realtek,rtl8366s"; target/linux/ath79/dts/ar9132_buffalo_wzr-hp-g300nh-s.dts: compatible = "realtek,rtl8366s"; target/linux/ath79/dts/ar9132_tplink_tl-wr1043nd-v1.dts: compatible = "realtek,rtl8366rb"; target/linux/ath79/dts/ar7242_tplink_tl-wr2543-v1.dts: compatible = "realtek,rtl8367"; Specially rtl8367 that is used just by a single device. Isn't it bloating the kernel for that target? Regards, --- Luiz Angelo Daros de Luca luizl...@gmail.com _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel