From: Armin Kuster <akuster@mvista.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ocp emac phy wierdness
Date: Thu, 22 Aug 2002 11:09:19 -0700 [thread overview]
Message-ID: <3D6528CF.90401@mvista.com> (raw)
In-Reply-To: 20020823071911.GF18818@zax
David,
The whole phy idea back when I did it was modeled after the fec.c driver
with the thought that at some point we could merge all phy_info structs
into a common file. The same idea was applied to the mii routines. I
noticed that code/information is duplicated in a few ethernet drivers in
ppc. Some of the what you see will be used when we add link support
driver, some of the 4xx boards with zmii bridges have interrupt
capability. The phy implementation is a project that is not completed. :)
Armin
David Gibson wrote:
>There seems to be a whole lot of stuff related to phy handling with no
>clear purpose to it. The table phy_cmd_config appears to be unused,
>as are the functions mii_queue_config, mii_display_config.
>
>Furthermore process_mii_queue() is dispatched through schedule_task(),
>from mii_queue_schedule(). But the only place that is called is in
>ppc405_enet_open(), which immediately calls schedule() to wait for the
>job to be completed. So what the hell is the point of the
>schedule_task() rigmarole?
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-22 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 7:19 ocp emac phy wierdness David Gibson
2002-08-22 18:09 ` Armin Kuster [this message]
2002-08-26 1:18 ` David Gibson
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=3D6528CF.90401@mvista.com \
--to=akuster@mvista.com \
--cc=david@gibson.dropbear.id.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).