From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/5] mpc83xx: mpc8360emds: Use RGMII mode, add workarounds for rev. 2.1 CPUs
Date: Fri, 18 Sep 2009 17:40:45 -0500 [thread overview]
Message-ID: <20090918174045.70d9d3da.kim.phillips@freescale.com> (raw)
In-Reply-To: <20090916192159.GD25296@oksana.dev.rtsoft.ru>
On Wed, 16 Sep 2009 23:21:59 +0400
Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
> This patch fixes various ethernet issues with gigabit links handling
> in U-Boot. The workarounds originally implemented by Kim Phillips for
> Linux kernel.
>
> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> ---
sorry, can't accept - this breaks r1.1 based boards:
U-Boot 2009.08-00210-g089732e (Sep 18 2009 - 17:25:22) MPC83XX
Reset Status: Software Hard, External/Internal Soft, External/Internal Hard
CPU: e300c1, MPC8360E, Rev: 1.1 at 528 MHz, CSB: 264 MHz
Board: Freescale MPC8360EMDS
I2C: ready
DRAM: 256 MB (DDR1, 64-bit, ECC off, 264 MHz)
SDRAM: 64 MB (local bus)
FLASH: 16 MB
In: serial
Out: serial
Err: serial
Net: FSL UEC0, FSL UEC1
Hit any key to stop autoboot: 0
=> tftp $loadaddr $uboot
UEC: PHY is Marvell 88E11x1 (1410cc2)
FSL UEC0: Full Duplex
FSL UEC0: Speed 1000BT
FSL UEC0: Link is up
Using FSL UEC0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.118
Filename 'kimphill/u-boot.MPC8360EMDS'.
Load address: 0x800000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
UEC: PHY is Marvell 88E11x1 (1410cc2)
warning: FSL UEC1: timeout on PHY link
FSL UEC0: Link is down
Kim
next prev parent reply other threads:[~2009-09-18 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 19:21 [U-Boot] [PATCH 4/5] mpc83xx: mpc8360emds: Use RGMII mode, add workarounds for rev. 2.1 CPUs Anton Vorontsov
2009-09-18 22:40 ` Kim Phillips [this message]
2009-09-18 23:29 ` Anton Vorontsov
2009-09-25 23:32 ` Kim Phillips
2009-09-26 0:33 ` Ben Warren
2009-09-26 0:47 ` Anton Vorontsov
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=20090918174045.70d9d3da.kim.phillips@freescale.com \
--to=kim.phillips@freescale.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