From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2][v2] powerpc/t2080qds: fixup dtb for 10g-kr
Date: Tue, 25 Nov 2014 09:44:03 -0800 [thread overview]
Message-ID: <5474BFE3.1010704@freescale.com> (raw)
In-Reply-To: <1413805699-14219-1-git-send-email-Shaohui.Xie@freescale.com>
On 10/20/2014 04:48 AM, Shaohui Xie wrote:
> XFI ports on t2080qds can work with fiber cable and direct attach
> cable(copper). We use hwconfig to define cable type for XFI, and fixup
> dtb based on the cable type.
>
> For copper cable, set below env in hwconfig:
>
> fsl_10gkr_copper:<10g_mac_name>
>
> the <10g_mac_name> can be fm1_10g1, fm1_10g2, fm1_10g3, fm1_10g4.
> fm1_10g1 stands for FM1-MAC9, fm1_10g2 stands for FM1-MAC10, fm1_10g3
> stands for FM1-MAC1, fm1_10g4 stands for FM1-MAC2. The four
> <10g_mac_name>s do not have to be coexist in hwconfig. For XFI ports, if
> a given 10G port will use the copper cable for 10GBASE-KR, set the
> <10g_mac_name> of the port in hwconfig, otherwise, fiber cable will be
> assumed to be used for the port.
>
> For ex. if four XFI ports will both use copper cable, the hwconfig
> should contain:
>
> fsl_10gkr_copper:fm1_10g1,fm1_10g2,fm1_10g3,fm1_10g4
>
> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
> ---
> changes for V2:
> add XFI description in t208xqds README.
> board/freescale/t208xqds/README | 23 ++++++++-
> board/freescale/t208xqds/eth_t208xqds.c | 86 +++++++++++++++++++++++++++++----
> 2 files changed, 98 insertions(+), 11 deletions(-)
>
Applied to u-boot-mpc85xx master. Awaiting upstream. Thanks.
York
prev parent reply other threads:[~2014-11-25 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 11:48 [U-Boot] [PATCH 1/2][v2] powerpc/t2080qds: fixup dtb for 10g-kr Shaohui Xie
2014-11-25 17:44 ` York Sun [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=5474BFE3.1010704@freescale.com \
--to=yorksun@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