netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Angelo Dureghello <angelo@kernel-space.org>, netdev@vger.kernel.org
Subject: Re: mv88e6321, dual cpu port
Date: Wed, 11 Jan 2023 00:02:07 +0100	[thread overview]
Message-ID: <Y73ub0xgNmY5/4Qr@lunn.ch> (raw)
In-Reply-To: <20230110222246.iy7m7f36iqrmiyqw@skbuf>

> > I cannot actually upgrade the kernel, due to cpu producer
> > customizations that are not mainlined, so would try to
> > downgrade the driver.
> 
> The delta between v5.4 and the kernel where support for multiple CPU
> ports was added is ~600 patches to the net/dsa/ folder alone. There are
> some non-trivial interdependencies with phylib, phylink, devlink, switchdev.
> You might also need support for the end result, if you end up cherry picking
> only what you think is useful. Hopefully that will help you reconsider.

v5.4 is really old, v5.10, v5.15 and v6.1 are also LTS kernels. I
suggest you ask your CPU vendor for a v6.1, or v5.15 port of their
vendor tree. v5.4 has a projected End Of Life December 2025, so if you
are going to invest a few months effort trying to get this working, do
you have enough time left to get some return on your investment? And a
plan what to do once it is EOL?

       Andrew

  reply	other threads:[~2023-01-10 23:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 20:40 mv88e6321, dual cpu port Angelo Dureghello
2023-01-09 21:33 ` Andrew Lunn
2023-01-10 10:23   ` Angelo Dureghello
2023-01-10 22:22     ` Vladimir Oltean
2023-01-10 23:02       ` Andrew Lunn [this message]
2023-01-23  8:52         ` Angelo Dureghello
2023-01-23 11:28           ` Vladimir Oltean
2023-01-23 13:26             ` Angelo Dureghello
2023-01-23 19:18               ` Vladimir Oltean
2023-01-23 20:08                 ` Andrew Lunn
2023-01-24  7:21                   ` Angelo Dureghello
2023-01-24 11:41                     ` Vladimir Oltean
2023-01-24 13:57                     ` Andrew Lunn
2023-01-25  9:04                       ` Angelo Dureghello
2023-02-06 10:43                       ` Angelo Dureghello
2023-02-06 13:24                         ` Andrew Lunn
2023-02-16 11:20                       ` Angelo Dureghello
2023-02-16 12:50                         ` Vladimir Oltean
2023-02-16 12:59                           ` Andrew Lunn
2023-02-16 15:31                             ` Vladimir Oltean
2023-02-16 18:39                               ` Angelo Dureghello
2023-02-18 13:30                                 ` Vladimir Oltean
2023-02-18 13:56                                   ` Russell King (Oracle)
2023-02-16 14:24                           ` Angelo Dureghello

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=Y73ub0xgNmY5/4Qr@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=angelo@kernel-space.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    /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).