linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Matus Ujhelyi <ujhelyi.m@gmail.com>,
	Michael Walle <michael@walle.cc>,
	Christoph Mattheis <christoph.mattheis@arcor.de>,
	acmattheis@gmx.net, linux-arm-kernel@lists.infradead.org
Subject: Re: Broken ethernet on SolidRun cubox-i
Date: Sun, 27 Dec 2020 19:07:44 +0100	[thread overview]
Message-ID: <20201227180744.GC3253993@lunn.ch> (raw)
In-Reply-To: <20201227161114.GF1551@shell.armlinux.org.uk>

> I wonder if we can just delete the phy-handle property, and list a
> PHY at both address 0 and 4 with the appropriate configuration...

Hi Russell, Michael

The Freescale FEC has an open coded version of phy_find_first(). So if
you don't have a phy-handle, it will go searching for a PHY on the
MDIO bus and should find it at 0 or 4.

     Andrew

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-12-27 18:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 12:18 Broken ethernet on SolidRun cubox-i Michael Walle
2020-12-26 12:34 ` Russell King - ARM Linux admin
2020-12-27 15:33   ` Michael Walle
2020-12-27 15:59     ` Michael Walle
2020-12-27 16:11       ` Russell King - ARM Linux admin
2020-12-27 18:07         ` Andrew Lunn [this message]
2021-01-08 11:53         ` Russell King - ARM Linux admin
2021-01-08 11:58           ` Michael Walle
2021-01-08 12:01             ` Russell King - ARM Linux admin
2021-01-08 12:14               ` Michael Walle
2021-01-08 12:25                 ` Christoph Mattheis
2021-01-08 12:27                   ` Russell King - ARM Linux admin
2021-01-08 12:33                     ` Christoph Mattheis
2021-01-08 12:37                 ` Russell King - ARM Linux admin
2021-01-08 12:51                   ` Michael Walle

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=20201227180744.GC3253993@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=acmattheis@gmx.net \
    --cc=christoph.mattheis@arcor.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael@walle.cc \
    --cc=ujhelyi.m@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).