netdev - Re: net-next lan9303 and CONFIG_NET_DSA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8DB857B3-F472-4D5D-AD66-27B3FA42ABBE@gmail.com>
Date:   Fri, 15 Dec 2017 12:06:01 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Egil Hjelmeland <privat@...l-hjelmeland.no>, andrew@...n.ch,
        Vivien Didelot <vivien.didelot@...oirfairelinux.com>
CC:     netdev <netdev@...r.kernel.org>
Subject: Re: net-next lan9303 and CONFIG_NET_DSA_LEGACY

On December 15, 2017 6:51:45 AM PST, Egil Hjelmeland <privat@...l-hjelmeland.no> wrote:
>Hi
>I found that our lan9303 board is unable to receive network data unless
>
>CONFIG_NET_DSA_LEGACY is set. Is that a problem with the driver, or our
>
>DTS?  (imx28)
>
>    ahb@...80000 {
>       mac0: ethernet@...f0000 {
>          clocks = <&clks 57>, <&clks 57>, <&clks 64>;
>          clock-names = "ipg", "ahb", "enet_out";
>          phy-mode = "rmii";
>          pinctrl-names = "default";
>          pinctrl-0 = <&mac0_pins_a>;
>          status = "okay";
>
>          fixed-link {
>             speed = <100>;
>             full-duplex;
>          };
>
>          mdio {
>             #address-cells = <1>;
>             #size-cells = <0>;
>
>             switch: switch-phy@0 {
>                compatible = "smsc,lan9303-mdio";
>                reg = <0>;
>                reset-gpios = <&gpio2 7 GPIO_ACTIVE_LOW >;
>                reset-duration = <10>;
>                ports {
>                   #address-cells = <1>;
>                   #size-cells = <0>;
>
>                   port@0 {
>                      reg = <0>;
>                      label = "cpu";
>                      ethernet = <&mac0>;
>                      phy-mode = "rmii";
>                      fixed-link {
>                         speed = <100>;
>                         full-duplex;
>                      };
>                   };
>
>                   port@1 { /* external port 1 */
>                      reg = <1>;
>                      label = "sw1";
>                      phy-mode = "rmii";
>                   };
>
>                   port@2 { /* external port 2 */
>                      reg = <2>;
>                      label = "sw2";
>                      phy-mode = "rmii";
>                   };
>                };
>             };
>          };
>       };
>    };
>
>Any advise would be appreciated.

Your DTS appears sane and using the new binding. Is the switch driver successfully probing and it is just packet transmission/reception that is non functional?
Hi Egil,
-- 
Florian