netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Jochen Friedrich <jochen@scram.de>
Cc: netdev@vger.kernel.org
Subject: Re: b53 tags on bpi-r1 (bcm53125)
Date: Tue, 21 Nov 2017 15:20:02 -0800	[thread overview]
Message-ID: <c7eb0575-0a94-9c59-0ebc-257a800f40c7@gmail.com> (raw)
In-Reply-To: <20171122000755.Horde.TwGdUCPMaJtOjf5NBNmIJXz@webmail.scram.de>

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

  reply	other threads:[~2017-11-21 23:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  8:10 b53 tags on bpi-r1 (bcm53125) Jochen Friedrich
2017-11-21 18:04 ` Florian Fainelli
2017-11-21 22:37   ` scram287
2017-11-21 23:07   ` Jochen Friedrich
2017-11-21 23:20     ` Florian Fainelli [this message]
2017-11-23 17:05       ` Jochen Friedrich
2017-11-23 17:18         ` Florian Fainelli
2017-11-23 19:14           ` Jochen Friedrich
2017-12-15  1:55             ` Florian Fainelli
2017-12-18 10:44               ` Jochen Friedrich
2017-12-29 20:21                 ` Florian Fainelli
2017-12-29 21:56                   ` Florian Fainelli
2017-12-30  3:22                     ` Florian Fainelli
2018-01-04  4:49                       ` Florian Fainelli
2018-01-08 16:51                         ` Jochen Friedrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c7eb0575-0a94-9c59-0ebc-257a800f40c7@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=jochen@scram.de \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).