public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@marvell.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] FW:  ARM Pull Request
Date: Thu, 23 Jul 2009 01:49:27 -0700	[thread overview]
Message-ID: <20090723084927.GC392@server.marvell.com> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202DE13BC79@SC-VEXCH1.marvell.com>

On Wed, Jul 22, 2009 at 11:44:57PM -0700, Prafulla Wadaskar wrote:

> > >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?
>
> But auto negotiation works with other board for similar case (i.e.
> mv88f6281gtw_ge)
> Only the difference is on rd6281A multichip addressing mode is used.
> I cannot comment much on this at this moment, this is my observation.
> So I was planning to debug this part.

In single-chip address mode, you'll still only be talking to one of
the five PHYs that the switch chip has, and things like forcing link
modes or checking whether the link is up will only work on one of
the five ports.

So if you're checking the PHY registers to make sure the link is up
before you e.g. start sending DHCP requests, then that won't do what
you want even though it will appear to work in single-chip address
mode.

If you're providing a way to force certain ports to certain speeds
from the uboot command line, then you should ideally just implement
multi-chip addressing mode and allow access to the individual PHYs,
I guess.

      parent reply	other threads:[~2009-07-23  8:49 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
2009-07-23  6:44       ` Prafulla Wadaskar
2009-07-23  7:00         ` Stefan Roese
2009-07-23  8:49         ` Lennert Buytenhek [this message]

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=20090723084927.GC392@server.marvell.com \
    --to=buytenh@marvell.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