From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] UEC phy not working on first try
Date: Wed, 20 Apr 2011 15:10:59 +0200 [thread overview]
Message-ID: <m2d3khgja4.fsf@ohwell.denx.de> (raw)
In-Reply-To: <2714_1303304270_4DAED84E_2714_10476_1_3CF34B583782C147807E09365F884DA430B91F7ACA@THSNCOA06MXS02P.ONE-06.GRP> (DUNDA Matthias's message of "Wed, 20 Apr 2011 14:57:43 +0200")
Hi Matthias,
>> >> > I am using u-boot.2010.09 on a MPC8568-based board.
>
>> Ah! I didn't realize that you are in the excellent position to have
>> one
>> good and one bad commit. Simply use git bisect to find the problematic
>> commit and show that to us.
>
> so far I traced it down to the adjust_link call in uec_init from file
> uec.c (line 1234 in release 2011.03).
>
> This call wasn't there in release 2009.11.1 and removing that line
> solves the issue here.
git blame shows this commit to be responsible:
commit 582c55a0274f38e6e7e35b95e7ab81d3e912f700
Author: Heiko Schocher <hs@denx.de>
Date: Wed Jan 20 09:04:28 2010 +0100
83xx, uec: split enet_interface in two variables
There's no sensible reason to unite speed and interface type into
one variable. So split this variable enet_interface into two
vars: enet_interface_type, which hold the interface type and speed.
Also: add the possibility for switching between 10 and 100 MBit
interfaces on the fly, when running in FAST_ETH mode.
Signed-off-by: Heiko Schocher <hs@denx.de>
Signed-off-by: Ben Warren <biggerbadderben@gmail.com>
> I don't know, why this went in and what the drawbacks are without
> it. Maybe someone on this list knows... (Sorry, I didn't search for a
> specific commit in git, yet. I just diffed pertinent files around the
> qe|uec|net drivers first.)
Hm, looking at adjust_link code, it seems that for you someone set
mii_info->link to 0 which gets you into the else clause of this
function. On a quick grep, I cannot find any place where this happens,
but I guess this is your problem (or at least one of them) ;)
Maybe Heiko can contribute some more insights?
> Happy sunny Easter all! 8-)
Same to you, thanks!
Detlev
--
There is no need to be rigid in carrying out policies about what changes
to install. To do a good job of maintaining Emacs doesn't require acting
like government bureaucrats.
-- Richard Stallman <E1MIx3Y-0005iZ-OH@fencepost.gnu.org>
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2011-04-20 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 8:04 [U-Boot] UEC phy not working on first try DUNDA Matthias
2011-04-19 15:22 ` Detlev Zundel
2011-04-20 6:06 ` DUNDA Matthias
2011-04-20 8:23 ` Detlev Zundel
2011-04-20 12:57 ` DUNDA Matthias
2011-04-20 13:10 ` Detlev Zundel [this message]
2011-04-20 13:46 ` Charles Krinke
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=m2d3khgja4.fsf@ohwell.denx.de \
--to=dzu@denx.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