From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Pawel Moll <pawel.moll@arm.com>,
"horms@verge.net.au" <horms@verge.net.au>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Mark Rutland <Mark.Rutland@arm.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"magnus.damm@gmail.com" <magnus.damm@gmail.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/4] ARM: shmobile: r8a7778: add Ether DT support
Date: Tue, 03 Sep 2013 17:53:13 +0400 [thread overview]
Message-ID: <5225E9C9.2060906@cogentembedded.com> (raw)
In-Reply-To: <2922765.My7X58lhxd@avalon>
Hello.
On 03-09-2013 16:11, Laurent Pinchart wrote:
>>> Documentation/devicetree/booting-without-of.txt mentions it, as well as a
>>> couple of other DT bindings document, but there's no clear documentation
>>> of what device_type should be for network device, and whether the property
>>> is mandatory or optional. Clarifying the documentation would be great.
>> It's documented in the ePAPR spec:
>> "The device_type property was used in IEEE 1275 to describe the device’s
>> FCode programming model. Because ePAPR does not have FCode, new use of
>> the property is deprecated, and it should be included only on cpu and
>> memory nodes for compatibility with IEEE 1275–derived device trees."
> Thank you for the clarification.
>> The bottom line is - don't use it, unless you've good good reasons?
> I'll let Sergei share his opinion on whether we've got good reasons :-)
No, we don't, I'll remove the prop.
WBR, Sergei
next prev parent reply other threads:[~2013-09-03 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201309010311.05466.sergei.shtylyov@cogentembedded.com>
2013-08-31 23:15 ` [PATCH 1/4] ARM: shmobile: r8a7778: add Ether DT support Sergei Shtylyov
2013-09-02 13:14 ` Laurent Pinchart
2013-09-02 14:05 ` Sergei Shtylyov
2013-09-02 14:18 ` Laurent Pinchart
2013-09-02 15:32 ` Pawel Moll
2013-09-03 12:11 ` Laurent Pinchart
2013-09-03 13:53 ` Sergei Shtylyov [this message]
2013-09-03 15:17 ` Magnus Damm
2013-09-03 18:27 ` Sergei Shtylyov
2013-09-04 5:35 ` Magnus Damm
2013-09-04 9:39 ` Laurent Pinchart
2013-09-05 6:03 ` Simon Horman
2013-08-31 23:22 ` [PATCH 3/4] ARM: shmobile: bockw-reference: " Sergei Shtylyov
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=5225E9C9.2060906@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=Mark.Rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=ian.campbell@citrix.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.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).