From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Fix for MII utils
Date: Mon, 20 Oct 2003 19:00:44 +0200 [thread overview]
Message-ID: <3F9414BC.8030701@imc-berlin.de> (raw)
Hi there,
the attached patch addresses two MII related issues:
a) mii info <addr> ignored <addr> and always showed info for 32 PHYs
b) The "Trick" mentioned in miiphy_info():
" * Trick: we are reading two 16 registers into a 32 bit variable
* so we do a 16 read into the high order bits of the variable (big
* endian, you know), shift it down 16 bits, and the read the rest."
does obviously not work on little endian machines.
* Patch by Steven Scholz, 20 Oct 2003
- "mii info <addr>" now only shows the info for PHY "addr" as the help
message already suggests
- Endian fix for miiphy_info()
Thanks,
Steven
next reply other threads:[~2003-10-20 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 17:00 Steven Scholz [this message]
2003-10-20 17:02 ` [U-Boot-Users] Re: Fix for MII utils Steven Scholz
2003-12-06 22:50 ` Wolfgang Denk
2003-10-20 19:22 ` [U-Boot-Users] " Wolfgang Denk
2003-10-21 5:39 ` Steven Scholz
2003-11-06 11:17 ` Steven Scholz
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=3F9414BC.8030701@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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