From: Paul Nasrat <pnasrat@redhat.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Jon Loeliger <jdl@jdl.com>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Add FSL CPM2 device tree node documentation
Date: Tue, 28 Mar 2006 11:55:10 -0500 [thread overview]
Message-ID: <1143564910.2660.4.camel@enki.eridu> (raw)
In-Reply-To: <20060328161431.18517.82573.stgit@vitb.ru.mvista.com>
On Tue, 2006-03-28 at 20:14 +0400, Vitaly Bordug wrote:
> Updated the documentation to include the initial description of the CPM2
> device that are used on PQII and PQIII families. Only initial sub-devices
> described so far, but that should be sufficient to move the respective
> boards to powerpc, with a reasonable minimum supporteddevice set.
>
> + 5) FCCs (Fast Communications Controllers)
> +
> + Required properties:
> +
> + - device_type : should be "network"
> + - model : "FCCx", x is typically a small number depending on the
> + devices amount
> + - compatible : should be "fs_enet"
> + - address : List of bytes representing the ethernet address of
> + this controller
Umm should we not use local-mac-address and mac-address (and
address-bits) as in section 3.7.4 in 1275-1994?
Paul
next prev parent reply other threads:[~2006-03-28 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 16:14 [PATCH] powerpc: Add FSL CPM2 device tree node documentation Vitaly Bordug
2006-03-28 16:37 ` Kumar Gala
2006-03-28 16:42 ` Vitaly Bordug
2006-03-28 16:55 ` Paul Nasrat [this message]
2006-04-12 23:19 ` Andy Fleming
2006-04-13 5:14 ` Paul Nasrat
2006-04-13 15:15 ` Jon Loeliger
2006-04-21 11:17 ` Paul Mackerras
2006-03-30 5:05 ` Dan Malek
2006-03-30 6:10 ` Paul Mackerras
2006-03-30 10:37 ` Vitaly Bordug
2006-03-30 10:26 ` Vitaly Bordug
2006-03-30 13:09 ` Dan Malek
2006-03-30 14:37 ` Kumar Gala
2006-03-30 15:14 ` Dan Malek
2006-03-30 15:02 ` Vitaly Bordug
2006-03-30 15:43 ` Kumar Gala
2006-03-30 15:10 ` Vitaly Bordug
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=1143564910.2660.4.camel@enki.eridu \
--to=pnasrat@redhat.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=vbordug@ru.mvista.com \
/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).