From: Florian Fainelli <f.fainelli@gmail.com>
To: Gerhard Wiesinger <lists@wiesinger.com>,
arm@lists.fedoraproject.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>, LKML <linux-kernel@vger.kernel.org>,
filbar@centrum.cz
Subject: Re: Banana Pi-R1 - kernel 5.6.0 and later broken - b43 DSA
Date: Sat, 20 Jun 2020 12:13:46 -0700 [thread overview]
Message-ID: <12ed4a27-7773-98c4-c8ba-f9b0d53a5b5f@gmail.com> (raw)
In-Reply-To: <912a58ac-6f81-ba22-c79e-f2bf902dae2e@wiesinger.com>
Hi,
On 6/20/2020 10:39 AM, Gerhard Wiesinger wrote:
> Hello,
>
> I'm having troubles with the Banana Pi-R1 router with newer kernels. No
> config changes, config works well since a lot of lernel updates ...
> Banana Pi-R1 is configured via systemd-networkd and uses the DSA
> (Distributed Switch Architecture) with b53 switch. No visible difference
> in interfaces, vlan config, bridge config, etc. Looks like actual
> configuration in the switch in the hardware is broken.
Can you share your network configuration again with me?
>
> # OK: Last good known version (booting that version is also ok)
> Linux bpi 5.5.18-200.fc31.armv7hl #1 SMP Fri Apr 17 17:25:00 UTC 2020
> armv7l armv7l armv7l GNU/Linux
OK, I suspect what has changed is this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8fab459e69abfd04a66d76423d18ba853fced4ab
which, if I remember your configuration correctly means that you now
have proper DSA interfaces and so all of the wan, lan1-lan4 interfaces
can now run a proper networking stack unlike before where you had to do
this via the DSA master network device (eth0). This also means that you
should run your DHCP server/client on the bridge master network device now.
>
> # NOK: no network
> Linux bpi 5.6.8-200.fc31.armv7hl #1 SMP Wed Apr 29 19:05:06 UTC 2020
> armv7l armv7l armv7l GNU/Linux
>
> # NOK: no network
> Linux bpi 5.6.0-300.fc32.armv7hl #1 SMP Mon Mar 30 16:37:50 UTC 2020
> armv7l armv7l armv7l GNU/Linux
>
> # NOK: no network
> Linux bpi 5.6.19-200.fc31.armv7hl #1 SMP Wed Jun 17 17:10:22 UTC 2020
> armv7l armv7l armv7l GNU/Linux
>
> # NOK: no network
> Linux bpi 5.7.4-200.fc32.armv7hl #1 SMP Fri Jun 19 00:52:22 UTC 2020
> armv7l armv7l armv7l GNU/Linux
>
>
> Saw that there were a lot of changes in the near past in the b53 driver:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/net/dsa/b53?h=v5.8-rc1+
>
>
>
> Any ideas?
>
> Thnx.
>
> Ciao,
> Gerhard
>
--
Florian
next prev parent reply other threads:[~2020-06-20 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 17:39 Banana Pi-R1 - kernel 5.6.0 and later broken - b43 DSA Gerhard Wiesinger
2020-06-20 19:13 ` Florian Fainelli [this message]
2020-06-20 19:37 ` Gerhard Wiesinger
2020-06-21 21:10 ` Florian Fainelli
2020-06-25 23:23 ` [fedora-arm] " Peter Robinson
2020-06-26 4:41 ` Florian Fainelli
2020-06-26 9:09 ` Peter Robinson
2020-06-26 15:46 ` Florian Fainelli
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=12ed4a27-7773-98c4-c8ba-f9b0d53a5b5f@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@lists.fedoraproject.org \
--cc=filbar@centrum.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@wiesinger.com \
--cc=maxime.ripard@bootlin.com \
--cc=wens@csie.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).