On 15.08.19 10:28, Serge Vasilugin wrote:
> From driver point of view no differance between rtl8367b and rtl8367s
> if it connected through EXT2 (rgmii only).
> So this trivial patch add some identification and initialization only.
> SGMII/HSGMII mode for EXT1 is not implemented for the sake of
On 15.08.19 10:28, Serge Vasilugin wrote:
> Both rtl8367b and rtl8367s have two extended interface
> rtl8367rb: 5 port + 2*RGMII/MII
> rtl8367s: 5 port + SGMII/HSGMI + RGMII/MII
> (?)rtl8367sb: 5 port + 2*RGMII/MII
> These interfaces correpond to EXT1 and EXT2 (ports 6 and 7 respectivly).
>
Hi Serge,
thank you very much for this contribution. I can only give some cosmetic
advice. I'm not sure about the functionality.
On 15.08.19 10:27, Serge Vasilugin wrote:
> By default rtl8366_smi use phy addr 0 at mii-bus to access switch registers.
> This patch allow to set it explicitly in
Hi!
On Thu, Aug 15, 2019 at 4:26 PM Serge Vasilugin wrote:
>
> Adding support for tplink archer c5 v4 some problems arise:
> 1. Device use unsupported rtl8367s switch.
> 2. rtl8367s switch have non default 0 phy address at mii-bus (29).
> 3. rtl8367s switch is connected through unsupported
Hi,
> [...]
> +
> + blobmsg_for_each_attr(option, options, rem) {
> + const char *prefix = "UPGRADE_OPT_";
> + char *name = malloc(strlen(prefix) +
> strlen(blobmsg_name(option)));
> + char value[11];
> + char *c;
> + int tmp;
> +
>
