From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound4-sin-R.bigfish.com (outbound-sin.frontbridge.com [207.46.51.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id 80E67DDE03 for ; Mon, 17 Dec 2007 15:58:24 +1100 (EST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C84069.70B415EE" Subject: RE: Device Tree updates for xilinx. Date: Sun, 16 Dec 2007 20:58:18 -0800 References: <20071204012811.AD70CEF004D@mail134-dub.bigfish.com> <20071213233945.E8FFAA6007C@mail180-sin.bigfish.com> <20071216070404.GK21311@localhost.localdomain> From: "Stephen Neuendorffer" To: "David Gibson" Message-Id: <20071217045726.DD1881298046@mail127-sin.bigfish.com> Cc: linuxppc-dev@ozlabs.org, Michal Simek , git List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C84069.70B415EE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Since there don't seem to be any examples of this in the tree: do you = have a format preference? For the rest of the compatible lists, I'm = using something like: xlnx,ipname-version. So for the microblaze, I'd = prefer something like: xlnx,microblaze-6.00.b For the powerpc, either ibm,ppc405 or ibm.ppc-405 would seem to be more = in character than PowerPC,405. Steve -----Original Message----- From: David Gibson [mailto:david@gibson.dropbear.id.au] Sent: Sat 12/15/2007 11:04 PM To: Stephen Neuendorffer Cc: Grant Likely; Michal Simek; John Williams; linuxppc-dev@ozlabs.org; = git Subject: Re: Device Tree updates for xilinx. =20 On Thu, Dec 13, 2007 at 03:41:16PM -0800, Stephen Neuendorffer wrote: >=20 > For reference, below is the device tree for a Virtex2Pro design. = Except > for the changes noted above, this is entirely automatically generated. >=20 > Steve >=20 > / { > mem_size_cells: #address-cells =3D <1>; > #size-cells =3D <1>; > compatible =3D "xlnx,virtex"; > model =3D "testing"; > DDR_256MB_32MX64_rank1_row13_col10_cl2_5: memory@0 { > device_type =3D "memory"; > reg =3D < 0 memsize:10000000 >; > } ; > chosen { > bootargs =3D "root=3D/dev/nfs > nfsroot=3D172.19.221.221:/exports/xup/ydl41 ip=3Ddhcp = console=3DttyUL0"; > } ; > cpus { > #address-cells =3D <1>; > #cpus =3D <1>; > #size-cells =3D <0>; > PowerPC,405@0 { I'm trying to encourage people to move to naming cpu nodes simply "cpu@XX", with the type of core in "compatible" instead - in keeping with the generic names convention used elsewhere. I think this will make your generator simpler, too. --=20 David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ = _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson ------_=_NextPart_001_01C84069.70B415EE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Device Tree updates for xilinx.

Since there don't seem to be any examples of this in = the tree: do you have a format preference?  For the rest of the = compatible lists, I'm using something like: xlnx,ipname-version.  = So for the microblaze, I'd prefer something like:

xlnx,microblaze-6.00.b

For the powerpc, either ibm,ppc405 or ibm.ppc-405 would seem to be more = in character than PowerPC,405.

Steve

-----Original Message-----
From: David Gibson [mailto:david@gibson.dropbear.= id.au]
Sent: Sat 12/15/2007 11:04 PM
To: Stephen Neuendorffer
Cc: Grant Likely; Michal Simek; John Williams; linuxppc-dev@ozlabs.org; = git
Subject: Re: Device Tree updates for xilinx.

On Thu, Dec 13, 2007 at 03:41:16PM -0800, Stephen Neuendorffer = wrote:

>
> For reference, below is the device tree for a Virtex2Pro = design.  Except
> for the changes noted above, this is entirely automatically = generated.
>
> Steve
>
> / {
>       mem_size_cells: #address-cells =3D = <1>;
>       #size-cells =3D <1>;
>       compatible =3D = "xlnx,virtex";
>       model =3D "testing";
>       = DDR_256MB_32MX64_rank1_row13_col10_cl2_5: memory@0 {
>       =         device_type =3D = "memory";
>       =         reg =3D < 0 = memsize:10000000 >;
>       } ;
>       chosen {
>       =         bootargs =3D = "root=3D/dev/nfs
> nfsroot=3D172.19.221.221:/exports/xup/ydl41 ip=3Ddhcp = console=3DttyUL0";
>       } ;
>       cpus {
>       =         #address-cells =3D = <1>;
>       =         #cpus =3D <1>;
>       =         #size-cells =3D = <0>;
>       =         PowerPC,405@0 {

I'm trying to encourage people to move to naming cpu nodes simply
"cpu@XX", with the type of core in "compatible" = instead - in keeping
with the generic names convention used elsewhere.  I think this = will
make your generator simpler, too.

--
David Gibson    =         =         | I'll have my music baroque, = and my code
david AT gibson.dropbear.id.au  | minimalist, thank you.  NOT = _the_ _other_
        =         =         =         | _way_ _around_!
http://www.ozlabs.org/~dgibson

------_=_NextPart_001_01C84069.70B415EE--