From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] FW: ARM Pull Request
Date: Thu, 23 Jul 2009 08:27:18 +0200 [thread overview]
Message-ID: <200907230827.18378.sr@denx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202DE13BC71@SC-VEXCH1.marvell.com>
On Thursday 23 July 2009 08:16:47 Prafulla Wadaskar wrote:
> > I'm working on the repo right now and should have another
> > pull request soon. The 'forced interface' patch is still
> > contentious, so isn't included.
>
> Okay
> With this for RD6281 Build will not fail, but network will be broken.
> Meanwhile I will check why auto negotiation doesn't work on this board?
Did you check if Lennert's comments are correct?
Quote:
>Isn't it just because on the RD6281A, the first ethernet MAC of the
>CPU is connected to an ethernet switch chip instead of an ethernet PHY,
>and therefore there is no negotiation to be done? (The second MAC
>is connected to a PHY directly, so that one should just use autoneg.)
>
>Even on the RD6281Z, we should just force the ethernet MAC to a
>fixed speed/duplex, since even though PHY polling might work there,
>we'll be talking to the PHY corresponding to the first switch port,
>which means that you might not be able to tftp from the second switch
>port or so if there's nothing plugged into the first one.
>
>FWIW, the linux kernel port also forces 1000/full on the CPU MACs where
>a switch chip is connected. On those CPU MACs where there is a switch
>chip connected, the (R)(G)MII interface becomes purely a bus to
>transport packets into and out of the crossbar, one that is always up.
So, is this ethernet port in question connected to switch? Then a forced link
(highest speed) should be used.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-07-23 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 5:54 [U-Boot] FW: ARM Pull Request Prafulla Wadaskar
2009-07-23 6:10 ` Ben Warren
2009-07-23 6:16 ` Prafulla Wadaskar
2009-07-23 6:17 ` Ben Warren
2009-07-23 6:27 ` Stefan Roese [this message]
2009-07-23 6:44 ` Prafulla Wadaskar
2009-07-23 7:00 ` Stefan Roese
2009-07-23 8:49 ` Lennert Buytenhek
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=200907230827.18378.sr@denx.de \
--to=sr@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