From: Grant Edwards <grant.b.edwards@gmail•com>
To: netdev@vger•kernel.org
Subject: Re: net: macb: fail when there's no PHY
Date: Thu, 3 Dec 2020 03:54:57 -0000 (UTC) [thread overview]
Message-ID: <rq9nih$egv$1@ciao.gmane.io> (raw)
In-Reply-To: 57728908-1ae3-cbe9-8721-81f06ab688b8@gmail.com
On 2020-12-03, Florian Fainelli <f.fainelli@gmail•com> wrote:
> You would have to have a local hack that intercepts the macb_ioctl()
> and instead of calling phylink_mii_ioctl() it would have to
> implement a custom ioctl() that does what
> drivers/net/phy/phy.c::phy_mii_ioctl does except the mdiobus should
> be pointed to the MACB MDIO bus instance and not be derived from the
> phy_device instance (because that one points to the fixed PHY).
So I can avoid my local hack to macb_main.c by doing a doing a local
hack to macb_main.c?
--
Grant
next prev parent reply other threads:[~2020-12-03 3:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 19:59 net: macb: fail when there's no PHY Grant Edwards
2017-09-21 20:05 ` Florian Fainelli
2017-09-21 20:36 ` Grant Edwards
2017-09-21 21:35 ` Brandon Streiff
2017-09-29 7:05 ` Harini Katakam
[not found] ` <CAK=1mW6Gti0QpUjirB6PfMCiQvnDjkbb56pVKkQmpCSkRU6wtA@mail.gmail.com>
2020-12-02 18:10 ` Florian Fainelli
2020-12-02 18:24 ` Grant Edwards
2020-12-02 18:35 ` Andrew Lunn
2020-12-02 19:16 ` Grant Edwards
2020-12-02 21:11 ` Andrew Lunn
2020-12-02 21:23 ` Grant Edwards
2020-12-03 2:39 ` Andrew Lunn
2020-12-03 3:03 ` Grant Edwards
2020-12-03 3:42 ` Florian Fainelli
2020-12-03 3:54 ` Grant Edwards [this message]
2020-12-03 4:07 ` Andrew Lunn
2020-12-03 15:07 ` Grant Edwards
2020-12-03 21:17 ` Andrew Lunn
2020-12-03 21:39 ` Grant Edwards
2020-12-03 21:49 ` Andrew Lunn
2020-12-03 22:20 ` Grant Edwards
2020-12-04 8:28 ` Alexander Dahl
2020-12-04 17:36 ` Andrew Lunn
2020-12-04 16:47 ` Florian Fainelli
2020-12-05 2:52 ` Grant Edwards
2020-12-05 3:06 ` Florian Fainelli
2020-12-03 4:00 ` Andrew Lunn
2020-12-02 18:10 ` Grant Edwards
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='rq9nih$egv$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/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