[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e29d955-2673-ea54-facb-3f96ce027e96@kernel-space.org>
Date: Mon, 23 Jan 2023 14:26:55 +0100 (CET)
From: Angelo Dureghello <angelo@...nel-space.org>
To: Vladimir Oltean <olteanv@...il.com>
cc: Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org
Subject: Re: mv88e6321, dual cpu port
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
Powered by blists - more mailing lists