linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Li Yang <leoli@freescale.com>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/83xx: Fix TSEC0 workability on MPC8313E-RDB boards
Date: Mon, 9 Feb 2009 15:47:47 +0800	[thread overview]
Message-ID: <2a27d3730902082347n7f0eb48dq8c4ecccda290f9c8@mail.gmail.com> (raw)
In-Reply-To: <20090205201040.GB3425@oksana.dev.rtsoft.ru>

On Fri, Feb 6, 2009 at 4:10 AM, Anton Vorontsov
<avorontsov@ru.mvista.com> wrote:
> TSEC0 is connected to Vitesse 7385 5-port switch. The switch
> isn't connected to any mdio bus, the link to the switch is fixed
> to Full-duplex 1000 Mb/s (no pause).

It's a complex case for RDB boards.  The revision A and revision B
boards DO always connect TSEC0 to Vitesse switch.  While the latest
revision C board has one setting to connect TSEC0 to a Marvell PHY and
MDIO bus.  In BSP we have several DTS's for each setting of the board,
shouldn't we do the same for upstream?

- Leo

  parent reply	other threads:[~2009-02-09  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 20:10 [PATCH 2/2] powerpc/83xx: Fix TSEC0 workability on MPC8313E-RDB boards Anton Vorontsov
2009-02-06 16:39 ` Kumar Gala
2009-02-09  7:47 ` Li Yang [this message]
2009-02-09 15:32   ` Kumar Gala
2009-02-10 15:10     ` [PATCH] powerpc/83xx: Revive Marvell PHY option on MPC8313E-RDB rev. C boards Anton Vorontsov
2009-02-10 15:30       ` Kumar Gala
2009-02-12  2:36         ` Li Yang-R58472
2009-02-12  5:25           ` Kumar Gala
2009-02-12  5:24       ` Kumar Gala
2009-02-12  5:40         ` Li Yang-R58472
2009-02-12 23:51           ` Kumar Gala
2009-02-13  1:18             ` Anton Vorontsov
2009-02-13  2:24               ` [PATCH] powerpc/83xx: Revive Marvell PHY option onMPC8313E-RDB " Li Yang-R58472

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=2a27d3730902082347n7f0eb48dq8c4ecccda290f9c8@mail.gmail.com \
    --to=leoli@freescale.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).