linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Andy Fleming <afleming@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Changed gianfar device tree definition to make it more flexible
Date: Wed, 08 Nov 2006 19:00:57 +0300	[thread overview]
Message-ID: <4551FF39.70701@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0611071707520.6936@ld0175-tx32.am.freescale.net>

Hello.

Andy Fleming wrote:

> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index 27b457c..bb1a402 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -1193,6 +1193,7 @@ platforms are moved over to use the flat
>  
>      - device_type : Should be "network"
>      - model : Model of the device.  Can be "TSEC", "eTSEC", or "FEC"
> +      (This is deprecated in favor of the feature bits)
>      - compatible : Should be "gianfar"
>      - reg : Offset and length of the register set for the device
>      - mac-address : List of bytes representing the ethernet address of
> @@ -1206,6 +1207,30 @@ platforms are moved over to use the flat
>        services interrupts for this device.
>      - phy-handle : The phandle for the PHY connected to this ethernet
>        controller.
> +    - interface : The interface this ethernet is using.  Current options are:
> +        GMII, MII, RGMII, SGMII, TBI, RMII, and RTBI
> +
> +  Optional properties (features):
> +    - gigabit : Indicates support for 1000 Mbit operation

    There's standard "supported-network-type" property listing supported
speeds/connectors already, why introduce another one?

WBR, Sergei

      parent reply	other threads:[~2006-11-08 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08  6:08 [PATCH] Changed gianfar device tree definition to make it more flexible Andy Fleming
2006-11-08  6:28 ` Kumar Gala
2006-11-08 23:57   ` Andy Fleming
2006-11-08 16:00 ` Sergei Shtylyov [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=4551FF39.70701@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=afleming@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).