From: Andrew Lunn <andrew@lunn•ch>
To: Alayev Michael <malayev@iai•co.il>
Cc: "'netdev@vger•kernel.org'" <netdev@vger•kernel.org>,
Dror Alon <adror@iai•co.il>, Efter Yoram <yefter@iai•co.il>
Subject: Re: dsa with 2 rgmii channels (1st is 2 switches & 2nd is phy)
Date: Fri, 9 Mar 2018 15:25:38 +0100 [thread overview]
Message-ID: <20180309142538.GC27783@lunn.ch> (raw)
In-Reply-To: <48F7D4389F30BA4383F214EE802BA47101706553F8@EXS10.iai.co.il>
On Fri, Mar 09, 2018 at 08:00:40AM +0000, Alayev Michael wrote:
> Hi Andrew,
>
> You have advised me to change the compatibility to "marvell,mv88e6190".
> The problem is that my linux version is Xilinx 4.4.0 (2016.2) - it contains mv88e6xxx driver files that do not support 6190 (though they do support 6085) and the driver has slightly different file tree.
> The closest Xilinx linux version that support this driver is 4.10.
>
> The thing is, I don't want to upgrade my linux version, just patch this driver module.
> Is it possible to do it in a simple way (windows like :) )?
To support a 6190, you need something much newer than 4.4. It does not
support the 6390 family. It took a lot of patches to make the 6390
work. 4.10 will mostly work, but the Ethernet PHYs might be broken, or
at least not use the Marvell PHY driver. And VLAN probably don't
work. But you don't want to use 4.10, it is a dead kernel, no security
fixes.
Ideally you want 4.14, which is a long term stable kernel.
Andrew
prev parent reply other threads:[~2018-03-09 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48F7D4389F30BA4383F214EE802BA471017065534C@EXS10.iai.co.il>
2018-03-04 15:31 ` dsa with 2 rgmii channels (1st is 2 switches & 2nd is phy) Andrew Lunn
2018-03-05 13:12 ` Alayev Michael
2018-03-05 14:15 ` Andrew Lunn
2018-03-09 8:00 ` Alayev Michael
2018-03-09 14:25 ` Andrew Lunn [this message]
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=20180309142538.GC27783@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=adror@iai$(echo .)co.il \
--cc=malayev@iai$(echo .)co.il \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yefter@iai$(echo .)co.il \
/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