From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: b53 tags on bpi-r1 (bcm53125) Date: Thu, 14 Dec 2017 17:55:57 -0800 Message-ID: References: <7c533a63-72e5-de68-99ff-8595492993a8@scram.de> <86b7ba4c-e632-f35b-647b-fdba93f2e0ed@gmail.com> <20171122000755.Horde.TwGdUCPMaJtOjf5NBNmIJXz@webmail.scram.de> <032d2ae0-0a57-6ba5-c0a0-704bd0885202@scram.de> <20171123201445.Horde.3FbuUT5FWgWtZrA-KljDJ7W@webmail.scram.de> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: Jochen Friedrich Return-path: Received: from mail-ot0-f175.google.com ([74.125.82.175]:38246 "EHLO mail-ot0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754628AbdLOB4B (ORCPT ); Thu, 14 Dec 2017 20:56:01 -0500 Received: by mail-ot0-f175.google.com with SMTP id p3so6618405oti.5 for ; Thu, 14 Dec 2017 17:56:00 -0800 (PST) In-Reply-To: <20171123201445.Horde.3FbuUT5FWgWtZrA-KljDJ7W@webmail.scram.de> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: Hi Jochen, On 11/23/2017 11:14 AM, Jochen Friedrich wrote: > Hi Florian, > >> With Broadcom tags (or any type of switch tagging protocol), eth0 >> becomes a conduit interface and no longer a "normal" network device for >> applications/socket to use. This means that if you were obtaining an IP >> address through a DHCP client using e.g: dhclient eth0, this now needs >> to be replaced using dhclient lan1 for instance. > > Yes, that's what I would expect. > >> If you use the per-port network devices, do you actually see Broadcom >> tags coming out of these interfaces, or is it just when you use eth0 >> like what you used before that you see that happening? > > For outgoing Packet, I see the tags on eth0, that's expected, but also > an a laptop connected to any of the external ports (no matter which one, > wan or lan1-4). > Incoming packets are seen on eth0 untagged and don't get forwarded to > the corresponding child Interface.> > So it seems the switch operates in dumb forwarding mode. Humm, what if you comment that part from b53_set_forwarding: b53_read8(dev, B53_CTRL_PAGE, B53_SWITCH_CTRL, &mgmt); mgmt |= B53_MII_DUMB_FWDG_EN; b53_write8(dev, B53_CTRL_PAGE, B53_SWITCH_CTRL, mgmt); does this help? > > I also tried a pull down on LED Port 0 (mii_dumb_fwdg_en), but the > switch still remains in dumb mode. However, I would have to double check > I picked the correct pin, the Bpi-r1 schematics is not completely error > free :-(. > > Thanks, Jochen -- Florian