From: Marek Behun <marek.behun@nic.cz>
To: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: secondary CPU port facing switch does not come up/online
Date: Mon, 22 Jun 2020 15:06:44 +0200 [thread overview]
Message-ID: <20200622150644.232e159b@nic.cz> (raw)
In-Reply-To: <50a02fb5-cb6c-5f37-150f-8ecfccdd473b@gmx.net>
On Mon, 22 Jun 2020 12:58:00 +0000
ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> Thank you for the input and pointer to patches.
>
> The problem is that it would require TOS deployed on the device, which
> is not the case and the repo being twice removed from the kernel source
> -> OpenWrt -> TOS, patches are neither available in mainline or OpenWrt
> whilst the Marvell SoC chipset is not unique to the CZ.NIC manufactured
> devices but leveraged by other vendors as well.
>
> It seems a bit strange to be nudged to the deployment of a particular
> repo, unless self-compiling kernel with those patch sets, instead of the
> same functionality being provided straight from mainline. Are those
> patch sets being introduced to mainline?
Hi,
I sent a RFC patch series last year adding multiCPU DSA to upstream
kernel, but the problem is a rather complicated. I plan to try again,
but do not know when.
As for OpenWRT - yes, we will try to add full support for Omnia into
upstream OpenWRT sometime soon. We were waiting for some other
patches to be accepted in upstream kernel.
Marek
next prev parent reply other threads:[~2020-06-22 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 20:24 secondary CPU port facing switch does not come up/online ѽ҉ᶬḳ℠
2020-06-21 21:08 ` Florian Fainelli
2020-06-22 7:39 ` ѽ҉ᶬḳ℠
2020-06-22 12:31 ` Marek Behun
2020-06-22 12:58 ` ѽ҉ᶬḳ℠
2020-06-22 13:06 ` Marek Behun [this message]
2020-06-22 13:23 ` ѽ҉ᶬḳ℠
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=20200622150644.232e159b@nic.cz \
--to=marek.behun@nic.cz \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vtol@gmx.net \
/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).