From: Andrew Lunn <andrew@lunn.ch>
To: Mason <slash.tmp@free.fr>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev <netdev@vger.kernel.org>, Mans Rullgard <mans@mansr.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Zach Brown <zach.brown@ni.com>, Shaohui Xie <shaohui.xie@nxp.com>,
Tim Beale <tim.beale@alliedtelesis.co.nz>,
Brian Hill <brian@houston-radar.com>,
Vince Bridgers <vbridgers2013@gmail.com>,
Balakumaran Kannan <kumaran.4353@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Sebastian Frias <sf84@laposte.net>,
Kirill Kapranov <kapranoff@inbox.ru>
Subject: Re: Debugging Ethernet issues
Date: Mon, 14 Nov 2016 14:34:28 +0100 [thread overview]
Message-ID: <20161114133428.GF26710@lunn.ch> (raw)
In-Reply-To: <5829BBFC.7040800@free.fr>
> How exactly does one use the generic PHY driver?
If there is no specific driver available for the PHY, linux will fall
back to the generic driver. So just don't compile the specific driver.
You can see under /sys/bus/mdio_bus/devices which driver is being
used.
Andrew
next prev parent reply other threads:[~2016-11-14 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 0:01 Debugging Ethernet issues Mason
2016-11-13 3:09 ` Andrew Lunn
2016-11-13 19:51 ` Mason
2016-11-13 19:55 ` Florian Fainelli
2016-11-14 13:03 ` Sebastian Frias
2016-11-14 13:28 ` Mason
2016-11-14 13:34 ` Andrew Lunn [this message]
2016-11-14 14:58 ` Mason
2016-11-14 15:33 ` Mason
2016-11-14 17:32 ` Florian Fainelli
2016-11-14 17:59 ` Sebastian Frias
2016-11-14 18:20 ` Florian Fainelli
2016-11-14 18:42 ` Florian Fainelli
2016-11-14 19:00 ` Måns Rullgård
2016-11-14 19:19 ` Florian Fainelli
2016-11-17 22:17 ` Måns Rullgård
2016-11-14 20:27 ` Mason
2016-11-14 21:00 ` Florian Fainelli
2016-11-14 22:48 ` Mason
2016-11-16 11:10 ` Sebastian Frias
2016-11-14 12:13 ` Mason
2016-11-14 12:45 ` Mason
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=20161114133428.GF26710@lunn.ch \
--to=andrew@lunn.ch \
--cc=brian@houston-radar.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kapranoff@inbox.ru \
--cc=kumaran.4353@gmail.com \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=sf84@laposte.net \
--cc=shaohui.xie@nxp.com \
--cc=slash.tmp@free.fr \
--cc=thomas.lendacky@amd.com \
--cc=tim.beale@alliedtelesis.co.nz \
--cc=vbridgers2013@gmail.com \
--cc=zach.brown@ni.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.