netdev - Re: b53 tags on bpi-r1 (bcm53125)

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: <c7eb0575-0a94-9c59-0ebc-257a800f40c7@gmail.com>
Date:   Tue, 21 Nov 2017 15:20:02 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Jochen Friedrich <jochen@...am.de>
Cc:     netdev@...r.kernel.org
Subject: Re: b53 tags on bpi-r1 (bcm53125)

On 11/21/2017 03:07 PM, Jochen Friedrich wrote:
> Hallo Florian,
> 
>> - what is the value of page 02, register 3 during b53_switch_detect()? A
>> managed switch should have this set to 0x3, whereas I would expect an
>> unmanaged switch to be 0x0
> 
> The register has the value 3.

OK, because this is a 53125S, it should support Broadcom tags correctly,
not clear yet what is happening. Just to make sure, you are using
arch/arm/boot/dts/sun7i-a20-lamobo-r1.dts as the DTS for this platform,
right?

If so, can you provide the ethtool -k eth0 output and/or see if
disabling HW VLAN tag support for eth0 helps in any way?
-- 
Florian