From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linus.walleij@linaro.org, ulli.kroll@googlemail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: gemini: sl3516: Mainlining of NS 2502
Date: Tue, 6 Apr 2021 11:06:55 +0200 [thread overview]
Message-ID: <YGwkr0qbYqR02Yyh@Red> (raw)
In-Reply-To: <YGt00DdrToMTskp8@lunn.ch>
Le Mon, Apr 05, 2021 at 10:36:32PM +0200, Andrew Lunn a écrit :
> On Mon, Apr 05, 2021 at 08:39:54PM +0200, Corentin Labbe wrote:
[ ... ]
> > libphy: Fixed MDIO Bus: probed
> > mdio-gpio ethernet-phy: failed to get alias id
>
> That does not look too good. But it is just a warning.
>
> if (pdev->dev.of_node) {
> bus_id = of_alias_get_id(pdev->dev.of_node, "mdio-gpio");
> if (bus_id < 0) {
> dev_warn(&pdev->dev, "failed to get alias id\n");
> bus_id = 0;
> }
>
> If you look at the example in the documentation, it has
>
> aliases {
> mdio-gpio0 = &mdio0;
> };
>
> If you add that, i guess this will go away.
>
Hello
Yes it go away with this
> > gemini-ethernet-port 6000c000.ethernet-port: probe 6000c000.ethernet-port ID 1
> > gemini-ethernet-port 6000c000.ethernet-port: using a random ethernet address
> > gemini-ethernet-port 6000c000.ethernet-port (unnamed net_device) (uninitialized): PHY init failed
>
> And now it seems to of all gone horribly wrong :-(
>
> This is the second Ethernet interface, the one you have commented as
>
> /* Not used in this platform */
>
> I _think_ you just need to delete the entry, otherwise it tried to
> probe it. And then that probe fails, it looks like it also fails the
> working interface :-(
Deleting the entry did no change. It still try to probe it.
I will try to delete second interface in gemini.dtsi just in case...
> > # udhcpc -i eth0
> > udhcpc: started, v1.33.0
> > udhcpc: socket: Address family not supported by protocol
>
> That suggests the kernel you have build does not have PF_PACKET.
> Enable CONFIG_PACKET_DIAG.
Yes adding it fixed this error message.
Thanks
_______________________________________________
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:[~2021-04-06 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 18:39 gemini: sl3516: Mainlining of NS 2502 Corentin Labbe
2021-04-05 20:36 ` Andrew Lunn
2021-04-06 9:06 ` Corentin Labbe [this message]
2021-04-06 8:15 ` Linus Walleij
2021-04-06 12:05 ` Corentin Labbe
2021-04-07 9:34 ` Linus Walleij
2021-05-05 19:26 ` Corentin Labbe
2021-05-05 23:56 ` Linus Walleij
2021-05-06 9:02 ` Daniel Palmer
2021-05-12 20:14 ` Corentin Labbe
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=YGwkr0qbYqR02Yyh@Red \
--to=clabbe.montjoie@gmail.com \
--cc=andrew@lunn.ch \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulli.kroll@googlemail.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).