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  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]
Date:   Sat, 5 Sep 2020 16:53:20 +0100
From:   Paul Barker <>
To:     Andrew Lunn <>
Cc:     Woojung Huh <>,
        Microchip Linux Driver Support <>,
        Vivien Didelot <>,
        Florian Fainelli <>,
        "David S . Miller" <>,
Subject: Re: [PATCH 3/4] net: dsa: microchip: Disable RGMII in-band status on KSZ9893

On Sat, 5 Sep 2020 at 16:32, Andrew Lunn <> wrote:
> On Sat, Sep 05, 2020 at 03:03:24PM +0100, Paul Barker wrote:
> > We can't assume that the link partner supports the in-band status
> > reporting which is enabled by default on the KSZ9893 when using RGMII
> > for the upstream port.
> What do you mean by RGMII inband status reporting? SGMII/1000BaseX has
> in band signalling, but RGMII?
>    Andrew

I'm referencing page 56 of the KSZ9893 datasheet
The datasheet says "The RGMII port will not function properly if IBS
is enabled in the switch, but it is not receiving in-band status from
a connected PHY." Since we can't guarantee all possible link partners
will support this it should be disabled. In particular, the IMX6 SoC
we're using with this switch doesn't support this on its Ethernet

I don't really know much about how this is implemented or how widely
it's supported.


Paul Barker
Konsulko Group

Powered by blists - more mailing lists