From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: LinuxPPC Embedded Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Better board support (was Re: [PATCH] Adding support for LXT971/2 PHYs)
Date: Fri, 05 May 2000 11:19:36 -0400 [thread overview]
Message-ID: <3912E688.70D4150D@embeddededge.com> (raw)
In-Reply-To: 20000505051936.BA2B23C971@elph.research.canon.com.au
Graham Stoney wrote:
> Another example under the scheme would be to replace most of the usages of
> "#ifdef CONFIG_RPXCLASSIC" in fec.c with "#ifdef PHY_QS6612",
Actually, that's already gone (but not yet checked in). I don't even
have #ifdefs for the PHYS. I scan the MII looking for all PHYs, when
one responds I match the mfg/device ID to a table and go.
There are thing unique to individual boards that still require board
specific #ifdefs.
> /* Ethernet : PHY controls - connected to port X
Many boards don't use 8xx I/O pins for PHY controls. They have
external hardware registers for this because they use the 8xx pins
for other communication I/O. This requires minor board specific
code to be included in the driver.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-05-05 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 7:01 [PATCH] Adding support for LXT971/2 PHYs Graham Stoney
2000-05-04 16:03 ` Dan Malek
2000-05-05 1:10 ` Graham Stoney
2000-05-05 3:08 ` Dan Malek
2000-05-05 5:19 ` Better board support (was Re: [PATCH] Adding support for LXT971/2 PHYs) Graham Stoney
2000-05-05 15:19 ` Dan Malek [this message]
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=3912E688.70D4150D@embeddededge.com \
--to=dan@netx4.com \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).