<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: Device Tree updates for xilinx.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Thanks, I've updated the generator to reflect this.<BR>
<BR>
Steve<BR>
<BR>
-----Original Message-----<BR>
From: David Gibson [<A HREF="mailto:david@gibson.dropbear.id.au">mailto:david@gibson.dropbear.id.au</A>]<BR>
Sent: Sun 12/16/2007 9:21 PM<BR>
To: Stephen Neuendorffer<BR>
Cc: linuxppc-dev@ozlabs.org; Michal Simek; git<BR>
Subject: Re: Device Tree updates for xilinx.<BR>
<BR>
On Sun, Dec 16, 2007 at 08:58:18PM -0800, Stephen Neuendorffer wrote:<BR>
><BR>
> Since there don't seem to be any examples of this in the tree: do<BR>
> you have a format preference? For the rest of the compatible lists,<BR>
> I'm using something like: xlnx,ipname-version. So for the<BR>
> microblaze, I'd prefer something like:<BR>
><BR>
> xlnx,microblaze-6.00.b<BR>
<BR>
Sounds reasonable.<BR>
<BR>
> For the powerpc, either ibm,ppc405 or ibm.ppc-405 would seem to be<BR>
> more in character than PowerPC,405.<BR>
<BR>
Well, we could list both forms, but PowerPC,405 should be included<BR>
since it's an established name. There's some history behind this:<BR>
before the generic names convention, the node name was used to encode<BR>
the most specific register interface for the device, and "compatible"<BR>
was used to describe any other interfaces it was also compatible with.<BR>
<BR>
With the generic names convention, the name came to represent the<BR>
general type of device, and "compatible" alone was used to describe<BR>
the programming interface(s). In Apple and IBM device trees, while<BR>
most things reflect the generic names convention, it seems the cpu<BR>
nodes were left using the old convention - which is why that approach<BR>
was copied and is currently used in all the dts files. So when<BR>
converting nodes to the generic names convention, the old content of<BR>
the node name should go into "compatible" verbatim as the first entry.<BR>
<BR>
In practice of course, I don't think anything looks at either the name<BR>
or the compatible property for cpu nodes (nor do I think they should)<BR>
- they'll just use the PVR.<BR>
<BR>
--<BR>
David Gibson | I'll have my music baroque, and my code<BR>
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_<BR>
| _way_ _around_!<BR>
<A HREF="http://www.ozlabs.org/~dgibson">http://www.ozlabs.org/~dgibson</A><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>