From: Willy Tarreau <w@1wt.eu>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: devicetree@vger.kernel.org, Baruch Siach <baruch@tkos.co.il>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [bug report] armada-8040-mcbin: 5.6-rc5 boot failure
Date: Tue, 14 Apr 2020 18:08:38 +0200 [thread overview]
Message-ID: <20200414160838.GA21435@1wt.eu> (raw)
In-Reply-To: <20200414160354.GA463339@curiosity>
Hi,
On Tue, Apr 14, 2020 at 07:03:54PM +0300, Sergey Matyukevich wrote:
> I have not changed configuration since 5.3, so all the marvell phy
> drivers are in place. Is there anything in configuration that could
> be missed after moving from 5.3 to 5.6 kernel ?
FWIW mine works perfectly fine with 5.4 at 1G/2.5G/10G. From what I can
quickly check here are the relevant parts in my config for ethernet (not
sure all are needed though):
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_MVMDIO=y
CONFIG_MVPP2=y
CONFIG_MDIO_DEVICE=y
CONFIG_MDIO_BUS=y
CONFIG_MDIO_BITBANG=y
CONFIG_MDIO_BUS_MUX=y
CONFIG_MDIO_BUS_MUX_MMIOREG=y
CONFIG_MDIO_BUS_MUX_MULTIPLEXER=y
CONFIG_MDIO_I2C=y
CONFIG_PHYLINK=y
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
CONFIG_SFP=y
CONFIG_FIXED_PHY=y
CONFIG_MARVELL_PHY=y
CONFIG_MARVELL_10G_PHY=y
Not tested 5.6 yet.
Hoping this helps,
Willy
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-14 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 22:05 [bug report] armada-8040-mcbin: 5.6-rc5 boot failure Sergey Matyukevich
2020-04-13 22:26 ` Russell King - ARM Linux admin
2020-04-14 16:03 ` Sergey Matyukevich
2020-04-14 16:08 ` Willy Tarreau [this message]
2020-04-14 16:55 ` Russell King - ARM Linux admin
2020-04-14 17:17 ` Willy Tarreau
2020-04-14 21:52 ` Sergey Matyukevich
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=20200414160838.GA21435@1wt.eu \
--to=w@1wt.eu \
--cc=baruch@tkos.co.il \
--cc=devicetree@vger.kernel.org \
--cc=geomatsi@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=miquel.raynal@bootlin.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).