From: "Shaun Jackman" <sjackman@gmail.com>
To: "David Keeffe" <david@systemsolve.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: External PHY in Linux smc91x driver
Date: Mon, 17 Dec 2007 11:50:12 -0700 [thread overview]
Message-ID: <7f45d9390712171050u751547daif8526807eae0cb8a@mail.gmail.com> (raw)
In-Reply-To: <4765ECCD.8030309@systemsolve.net>
Hello David, (cc'ed to LKML)
The patch, `smc91x: Add support for an external PHY' from 2006-07-19,
worked for me. It simply set the extphy bit of the smc91x to disable
the internal PHY and use the external MII interface. As you can see
from the patch, it doesn't support configuring the external PHY in any
way. Most PHYs power up to a default functional state. In further
work, someone could add the smc91x MII configuration interface to the
PHY abstraction layer. Incidentally, the PHY I was using (an unmanaged
switch chip) didn't even support configuration over the MII interface.
Apply this patch first as a minimum first measure. Test the patch, if
it works for you, sign off on it and repost it to the LKML.
Cheers,
Shaun
On Dec 16, 2007 8:28 PM, David Keeffe <david@systemsolve.net> wrote:
> Hi Shaun
>
> I've been asked to look at supporting an external (LXT) PHY for the
> SMC91x driver, and I noticed that you have published a patch for this.
> Is that all that's needed to make the SMC chip work with an external
> PHY? Presumably there are also parts which actually do the phy setup (if
> it's not an SMC component).
>
> I've been considering changing the driver to use the PHY abstraction
> layer, but that seems a big job if the problem has already been solved!
>
> Would you care to share what you've achieved?
>
> David Keeffe
parent reply other threads:[~2007-12-17 18:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4765ECCD.8030309@systemsolve.net>]
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=7f45d9390712171050u751547daif8526807eae0cb8a@mail.gmail.com \
--to=sjackman@gmail.com \
--cc=david@systemsolve.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®