From: Angelo Dureghello <angelo@kernel-space.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, netdev@vger.kernel.org
Subject: Re: mv88e6321, dual cpu port
Date: Mon, 23 Jan 2023 14:26:55 +0100 (CET) [thread overview]
Message-ID: <7e29d955-2673-ea54-facb-3f96ce027e96@kernel-space.org> (raw)
In-Reply-To: <20230123112828.yusuihorsl2tyjl3@skbuf>
Hi Vladimir,
On Mon, 23 Jan 2023, Vladimir Oltean wrote:
> On Mon, Jan 23, 2023 at 09:52:15AM +0100, Angelo Dureghello wrote:
>> I am now stuck to 5.4.70 due to freescale stuff in it.
>> I tried shortly a downgrade of net/dsa part from 5.5,
>> but, even if i have no errors, i can't ping out, something
>> seems has gone wrong, i don't like too much this approach.
>>
>> But of course, i could upgrade to 5.10 that's available
>> from freescale, with some effort.
>> Then, i still should apply a patch on the driver to have dual
>> cpu running, if i understand properly, correct ?
>
> What is the Freescale chip stuck on 5.4 (5.10 with some effort) if I may
> ask? I got the impression that the vast majority of SoCs have good
> enough mainline support to boot a development kernel and work on that,
> the exception being some S32 platforms.
>
I think i tested mainline kernel, but the rpmsg part to
communicate with M4 core and scu firmware seems not there.
So i am stuck with freescale stuff now. Anyway, freescale
released their 5.10 branch, so eventually i'll move
to that.
Regards,
angelo
next prev parent reply other threads:[~2023-01-23 13:26 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
2023-01-23 8:52 ` Angelo Dureghello
2023-01-23 11:28 ` Vladimir Oltean
2023-01-23 13:26 ` Angelo Dureghello [this message]
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=7e29d955-2673-ea54-facb-3f96ce027e96@kernel-space.org \
--to=angelo@kernel-space.org \
--cc=andrew@lunn.ch \
--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).