From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] mii_phy.h
Date: Thu, 25 Aug 2011 09:25:32 +0200 [thread overview]
Message-ID: <4E55F8EC.50001@monstr.eu> (raw)
Hi,
Can someone clear me purpose of mii_phy.h? It looks like that it is really
ancient file which hasn't been touched from 2003.
It is use for two files
[monstr at monstr u-boot]$ grep -rn "mii_phy.h" *
board/ep8260/mii_phy.c:2:#include <mii_phy.h>
board/rpxsuper/mii_phy.c:2:#include <mii_phy.h>
+ different numbers of arguments against new "version"
[monstr at monstr u-boot]$ grep -rn "mii_discover_phy" *
arch/m68k/include/asm/fec.h:359:int mii_discover_phy(struct eth_device *dev);
arch/powerpc/cpu/mpc8xx/fec.c:63:static int mii_discover_phy(struct eth_device *dev);
arch/powerpc/cpu/mpc8xx/fec.c:728: efis->actual_phy_addr = mii_discover_phy (dev);
arch/powerpc/cpu/mpc8xx/fec.c:872:static int mii_discover_phy(struct eth_device *dev)
arch/powerpc/cpu/mpc85xx/ether_fcc.c:237: mii_discover_phy();
arch/powerpc/cpu/mpc8260/ether_fcc.c:234: mii_discover_phy();
board/ep8260/mii_phy.c:10:mii_discover_phy(void)
board/rpxsuper/mii_phy.c:10:mii_discover_phy(void)
drivers/net/mcfmii.c:150:int mii_discover_phy(struct eth_device *dev)
drivers/net/mcfmii.c:253: info->phy_addr = mii_discover_phy(dev);
include/mii_phy.h:4:void mii_discover_phy(void);
+ that functions without arg are not called either
arch/powerpc/cpu/mpc85xx/ether_fcc.c:237: mii_discover_phy();
arch/powerpc/cpu/mpc8260/ether_fcc.c:234: mii_discover_phy();
I found that Frank Panno is ep8260 maintainer. Any comment?
The best will be to remove mii_phy entirely.
Wolfgang: What do you think?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next reply other threads:[~2011-08-25 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 7:25 Michal Simek [this message]
2011-08-25 14:20 ` [U-Boot] mii_phy.h Mike Frysinger
2011-08-26 6:19 ` Michal Simek
2011-08-26 6:36 ` Wolfgang Denk
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=4E55F8EC.50001@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.de \
/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.