From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx•com>
To: "Grant Likely" <grant.likely@secretlab•ca>,
<linuxppc-dev@ozlabs•org>,
"Wolfgang Reissnegger" <wre@xilinx•com>,
"Leonid" <Leonid@a-k-a•net>, <microblaze-uclinux@itee•uq.edu.au>
Subject: RE: [PATCH v2] Device tree bindings for Xilinx devices
Date: Tue, 16 Oct 2007 16:23:39 -0700 [thread overview]
Message-ID: <20071016232404.5F4D51130091@mail133-blu.bigfish.com> (raw)
In-Reply-To: <20071015155223.7403.39615.stgit@trillian.cg.shawcable.net>
It occurs to me that the 'compatible' bindings should probably be the
name of the preferred driver for the device.=20
> + l) Xilinx ML300 Framebuffer
> + - compatible : Must include "xilinx,ml300-fb"
Should probably be 'xilinxfb', and probably shouldn't reference ML300 at
all.
> + n) Xilinx EMAC and Xilinx TEMAC
> +
> + Xilinx Ethernet devices. Uses common properties from=20
> other Ethernet
> + devices with the following constraints:
> + =20
> + Required properties:
> + - compatible : Must include one of: "xilinx,plb-temac",
> + "xilinx,plb-emac", "xilinx-opb-emac"
Should probably be just 'emac' and 'temac'.
This should be possible to extract using Michel Simek's EDK-integrated
device tree generator. The compatibility information is stored in the
EDK driver's .mdd file (although this is somewhat backwards from what
one might expect).
Steve
next prev parent reply other threads:[~2007-10-16 23:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 15:53 [PATCH v2] Device tree bindings for Xilinx devices Grant Likely
2007-10-15 19:21 ` Arnd Bergmann
2007-10-15 19:54 ` Grant Likely
2007-10-16 18:24 ` Stephen Neuendorffer
2007-10-16 19:36 ` Grant Likely
2007-10-17 0:21 ` Stephen Neuendorffer
2007-10-17 2:35 ` Grant Likely
2007-10-17 3:03 ` Grant Likely
2007-10-16 23:23 ` Stephen Neuendorffer [this message]
2007-10-17 1:49 ` Josh Boyer
2007-10-17 2:31 ` Grant Likely
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=20071016232404.5F4D51130091@mail133-blu.bigfish.com \
--to=stephen.neuendorffer@xilinx$(echo .)com \
--cc=Leonid@a-k-a$(echo .)net \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
--cc=wre@xilinx$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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