From: Simon Yang <bestwish.simon@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Can't get correct VSC8201 PHYID on MPC8347 in uboot-1.1.3 issue
Date: Tue, 29 Nov 2005 01:14:51 +0800 [thread overview]
Message-ID: <1c3e00040511280914r2f72c0a5g@mail.gmail.com> (raw)
Dear All,
Now I use VSC8201PHY on MPC8347 with uboot-1.1.3,I think VSC8201 PHY
is similar to CIS8201PHY,so I add struct phy_info_vsc8201 based on
struct phy_info_cis8201 in tsec.c and related registers in tsec.h, but
during bootup I meet below problem in tsec.c when it goes to read
phy_id in function read_phy_reg(), the phy_id is always ffffffff, the
log file is as follow:
Net: TSEC initialize begin...
In Read reg func PHY ID is:0
Register number MIIMADD is 2
PHY Reg after read PHYIR1 is:ffff
PHY Reg High 16 bit is:ffff0000
Begin Read phy reg!
In Read reg func PHY ID is:0
Register number MIIMADD is 3
PHY Reg after read PHYIR2 is:ffff
Tsec: read from reg is ffffffff
Freescale TSEC0: PHY id ffffffff is not supported!
Freescale TSEC0: No PHY found
TSEC initialize begin...
In Read reg func PHY ID is:1
Register number MIIMADD is 102
PHY Reg after read PHYIR1 is:ffff
PHY Reg High 16 bit is:ffff0000
Begin Read phy reg!
In Read reg func PHY ID is:1
Register number MIIMADD is 103
PHY Reg after read PHYIR2 is:ffff
Tsec: read from reg is ffffffff
Freescale TSEC1: PHY id ffffffff is not supported!
Freescale TSEC1: No PHY found
Freescale TSEC0, Freescale TSEC1
Thanks in advance.
Best Regards
SImon
next reply other threads:[~2005-11-28 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 17:14 Simon Yang [this message]
2005-11-28 17:28 ` [U-Boot-Users] Re: Can't get correct VSC8201 PHYID on MPC8347 in uboot-1.1.3 issue David Updegraff
2005-11-29 2:19 ` Simon Yang
2005-11-29 13:05 ` Simon Yang
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=1c3e00040511280914r2f72c0a5g@mail.gmail.com \
--to=bestwish.simon@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox