From: afaerber@suse•de (Andreas Färber)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v3] ARM: dts: turris-omnia: add support for ethernet switch
Date: Wed, 4 Jan 2017 11:49:12 +0100 [thread overview]
Message-ID: <e1dae939-e209-eccc-00df-b996d03cb8db@suse.de> (raw)
In-Reply-To: <20170103193501.4827-1-uwe@kleine-koenig.org>
Hi Uwe,
Am 03.01.2017 um 20:35 schrieb Uwe Kleine-K?nig:
> The Turris Omnia features a Marvell MV88E6176 ethernet switch. Add it to
> the dts.
>
> Signed-off-by: Uwe Kleine-K?nig <uwe@kleine-koenig•org>
It's still not working for me on next-20170104 with this v3.
Are there any other patches needed?
Should all ports LAN0-LAN4 work with the commented-out second cpu node?
I've been using the WAN port (eth2) just fine. (=eth1 in OpenWrt)
With this patch, eth0 and eth1 are shown as UP by default. If however I
enslave eth0 and eth1 in a br-lan bridge, as seen under OpenWrt for
eth0+eth2, then eth1 is DOWN while eth0 remains UP, and br-lan remains
DOWN. Same issue if I drop eth0 from the bridge - after a reboot eth1 is
UP but br-lan is still DOWN.
I had to manually enable CONFIG_BRIDGE, so maybe I'm missing more kernel
options? Or did you simply not try using a bridge?
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2017-01-04 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 9:43 [PATCH v2] ARM: dts: turris-omnia: add support for ethernet switch Uwe Kleine-König
2017-01-03 15:21 ` Andrew Lunn
2017-01-03 19:35 ` [PATCH v3] " Uwe Kleine-König
2017-01-03 20:10 ` Andrew Lunn
2017-01-04 10:49 ` Andreas Färber [this message]
2017-01-04 13:41 ` Andrew Lunn
2017-01-05 12:40 ` Andreas Färber
2017-01-05 12:57 ` Gregory CLEMENT
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=e1dae939-e209-eccc-00df-b996d03cb8db@suse.de \
--to=afaerber@suse$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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