From: David Gibson <david@gibson.dropbear.id.au>
To: Armin Kuster <akuster@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: ocp emac phy wierdness
Date: Fri, 23 Aug 2002 17:19:11 +1000 [thread overview]
Message-ID: <20020823071911.GF18818@zax> (raw)
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?
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-08-23 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 7:19 David Gibson [this message]
2002-08-22 18:09 ` ocp emac phy wierdness Armin Kuster
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=20020823071911.GF18818@zax \
--to=david@gibson.dropbear.id.au \
--cc=akuster@mvista.com \
--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).