Virtex V5FX PPC 440 Support In Xilinx Git Tree

Virtex V5FX PPC 440 Support In Xilinx Git Tree

[John Linn]

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

I pushed PowerPC 440 support to the Xilinx Git server with support for
ppc arch and with powerpc arch support coming in the near future. 

 

A default kernel configuration file, ml507_defconfig, is provided in the
kernel tree to support the Xilinx ML507 board with the PowerPC 440.

 

Thanks,

John

 

 


[-- Attachment #2: Type: text/html, Size: 7503 bytes --]

Re: Virtex V5FX PPC 440 Support In Xilinx Git Tree

[Grant Likely]

On Tue, Apr 1, 2008 at 5:41 PM, John Linn <John.Linn@xilinx.com> wrote:
>
>
>
>
> I pushed PowerPC 440 support to the Xilinx Git server with support for ppc
> arch and with powerpc arch support coming in the near future.

Cool, I look forward to playing with it...

/me just needs to find a client who needs him to do V5 work.  :-)

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

Re: Virtex V5FX PPC 440 Support In Xilinx Git Tree

[Peter Korsgaard]

>>>>> "John" == John Linn <John.Linn@xilinx.com> writes:

 John> I pushed PowerPC 440 support to the Xilinx Git server with
 John> support for ppc arch and with powerpc arch support coming in
 John> the near future.

Neat, but why have you added arch/ppc support? It's supposed to go
away pretty much by the time the hardware gets in the hand of
developers.

-- 
Bye, Peter Korsgaard

RE: Virtex V5FX PPC 440 Support In Xilinx Git Tree

[John Linn]

Hi Peter,

We added arch/ppc support because it was the easiest path for us.  We
realize it's going away soon in the mainline.

We are working on getting arch/powerpc more mature for both the 405 and
the 440 as we do believe this is the future for powerpc.

Thanks,
John



-----Original Message-----
From: Peter Korsgaard [mailto:jacmet@gmail.com] On Behalf Of Peter
Korsgaard
Sent: Wednesday, April 02, 2008 3:51 AM
To: John Linn
Cc: linuxppc-embedded@ozlabs.org; git
Subject: Re: Virtex V5FX PPC 440 Support In Xilinx Git Tree

>>>>> "John" =3D=3D John Linn <John.Linn@xilinx.com> writes:

 John> I pushed PowerPC 440 support to the Xilinx Git server with
 John> support for ppc arch and with powerpc arch support coming in
 John> the near future.

Neat, but why have you added arch/ppc support? It's supposed to go
away pretty much by the time the hardware gets in the hand of
developers.

--=20
Bye, Peter Korsgaard

RE: Virtex V5FX PPC 440 Support In Xilinx Git Tree

[Stephen Neuendorffer]

I've just pushed support for generating device trees for the ppc440 in
V5FXT up to git.xilinx.com.

The most obvious difference is that the PPC440 block contains not only
the PPC440 core, but also an interconnect block, subsuming part of the
'multi-ported' functionality of the MPMC.  In order to have a relatively
straightforward mapping between blocks in the EDK design and nodes in
the dts, I've represented this as shown below.  Note that unlike the
MPMC, the dma ports are controlled through DCR (which is part of the
point of the recent dcr patches).  I've done some preliminary testing
using some hacked together platform support code and we'll update this
based on the 405 code soon.

Steve

/ {
	#address-cells =3D <1>;
	#size-cells =3D <1>;
	compatible =3D "xlnx,virtex";
	dcr-parent =3D <&ppc440_virtex5_0>;
	model =3D "testing";
	chosen {
		bootargs =3D "root=3D/dev/xsysace/disc0/part2";
	} ;
	cpus {
		#address-cells =3D <1>;
		#cpus =3D <1>;
		#size-cells =3D <0>;
		ppc440_virtex5_0: cpu@0 {
			#address-cells =3D <1>;
			#size-cells =3D <1>;
			clock-frequency =3D <17d78400>;
			compatible =3D "PowerPC,440", "ibm,ppc440";
			d-cache-line-size =3D <20>;
			d-cache-line-size =3D <20>;
			d-cache-size =3D <8000>;
			dcr-access-method =3D "native";
			dcr-controller ;
			device_type =3D "cpu";
			i-cache-line-size =3D <20>;
			i-cache-size =3D <8000>;
			model =3D "PowerPC,440";
			reg =3D <0>;
			timebase-frequency =3D <17d78400>;
			DMA0: sdma@1010000 {
				compatible =3D "xlnx,ll-dma-1.00.a";
				dcr-reg =3D < 1010000 11 >;
				interrupt-parent =3D <&opb_intc_0>;
				interrupts =3D < 5 2 6 2 >;
			} ;
			DMA1: sdma@1010000 {
				compatible =3D "xlnx,ll-dma-1.00.a";
				dcr-reg =3D < 1010000 11 >;
			} ;
			DMA2: sdma@1010000 {
				compatible =3D "xlnx,ll-dma-1.00.a";
				dcr-reg =3D < 1010000 11 >;
			} ;
			DMA3: sdma@1010000 {
				compatible =3D "xlnx,ll-dma-1.00.a";
				dcr-reg =3D < 1010000 11 >;
			} ;
		} ;
	} ;
	plb_v46_cfb_0: plb@0 {
		#address-cells =3D <1>;
		#size-cells =3D <1>;
		compatible =3D "xlnx,plb-v46-1.00.a";
		ranges ;
		iic_bus: i2c@d0020000 {
			compatible =3D "xlnx,xps-iic-1.00.a";
			interrupt-parent =3D <&opb_intc_0>;
			interrupts =3D < 7 2 >;
			reg =3D < d0020000 200 >;
			xlnx,clk-freq =3D <5f5e100>;
			xlnx,family =3D "virtex5";
			xlnx,gpo-width =3D <1>;
			xlnx,iic-freq =3D <186a0>;
			xlnx,ten-bit-adr =3D <0>;
		} ;
		leds_8bit: gpio@d0010200 {
			compatible =3D "xlnx,xps-gpio-1.00.a";
			interrupt-parent =3D <&opb_intc_0>;
			interrupts =3D < 1 2 >;
			reg =3D < d0010200 200 >;
			xlnx,all-inputs =3D <0>;
			xlnx,all-inputs-2 =3D <0>;
			xlnx,dout-default =3D <0>;
			xlnx,dout-default-2 =3D <0>;
			xlnx,family =3D "virtex5";
			xlnx,gpio-width =3D <8>;
			xlnx,interrupt-present =3D <1>;
			xlnx,is-bidir =3D <1>;
			xlnx,is-bidir-2 =3D <1>;
			xlnx,is-dual =3D <0>;
			xlnx,tri-default =3D <ffffffff>;
			xlnx,tri-default-2 =3D <ffffffff>;
		} ;
		ll_temac_0: xps-ll-temac@91200000 {
			#address-cells =3D <1>;
			#size-cells =3D <1>;
			compatible =3D "xlnx,compound";
			ethernet@91200000 {
				compatible =3D "xlnx,xps-ll-temac-1.00.b";
				device_type =3D "network";
				interrupt-parent =3D <&opb_intc_0>;
				interrupts =3D < 4 2 >;
				llink-connected =3D <&DMA0>;
				local-mac-address =3D [ 00 00 00 00 00 00
];
				reg =3D < 91200000 40 >;
				xlnx,bus2core-clk-ratio =3D <1>;
				xlnx,phy-type =3D <1>;
				xlnx,phyaddr =3D <1>;
				xlnx,rxcsum =3D <0>;
				xlnx,rxfifo =3D <4000>;
				xlnx,temac-type =3D <0>;
				xlnx,txcsum =3D <0>;
				xlnx,txfifo =3D <4000>;
			} ;
		} ;
		opb_intc_0: interrupt-controller@d0020200 {
			#interrupt-cells =3D <2>;
			compatible =3D "xlnx,xps-intc-1.00.a";
			interrupt-controller ;
			reg =3D < d0020200 20 >;
			xlnx,num-intr-inputs =3D <8>;
		} ;
		plb_bram_if_cntlr_0: xps-bram-if-cntlr@ffff0000 {
			compatible =3D "xlnx,xps-bram-if-cntlr-1.00.a";
			reg =3D < ffff0000 10000 >;
			xlnx,family =3D "virtex5";
		} ;
		plb_bram_if_cntlr_1: xps-bram-if-cntlr@eee00000 {
			compatible =3D "xlnx,xps-bram-if-cntlr-1.00.a";
			reg =3D < eee00000 2000 >;
			xlnx,family =3D "virtex5";
		} ;
		rs232_uart_0: serial@d0000000 {
			clock-frequency =3D "";
			compatible =3D "xlnx,xps-uart16550-1.00.a";
			current-speed =3D <2580>;
			device_type =3D "serial";
			interrupt-parent =3D <&opb_intc_0>;
			interrupts =3D < 0 2 >;
			reg =3D < d0000000 2000 >;
			reg-offset =3D <3>;
			reg-shift =3D <2>;
			xlnx,family =3D "virtex5";
			xlnx,has-external-rclk =3D <0>;
			xlnx,has-external-xin =3D <1>;
			xlnx,is-a-16550 =3D <1>;
		} ;
		sysace_compactflash: sysace@d0030100 {
			compatible =3D "xlnx,xps-sysace-1.00.a";
			reg =3D < d0030100 80 >;
			xlnx,family =3D "virtex5";
			xlnx,mem-width =3D <10>;
		} ;
	} ;
	ppc440mc_ddr2_0: memory@0 {
		device_type =3D "memory";
		reg =3D < 0 20000000 >;
	} ;
}  ;

> -----Original Message-----
> From: John Linn
> Sent: Wednesday, April 02, 2008 8:24 AM
> To: Peter Korsgaard
> Cc: linuxppc-embedded@ozlabs.org; git
> Subject: RE: Virtex V5FX PPC 440 Support In Xilinx Git Tree
>=20
> Hi Peter,
>=20
> We added arch/ppc support because it was the easiest path for us.  We
realize it's going away soon in
> the mainline.
>=20
> We are working on getting arch/powerpc more mature for both the 405
and the 440 as we do believe this
> is the future for powerpc.
>=20
> Thanks,
> John
>=20
>=20
>=20
> -----Original Message-----
> From: Peter Korsgaard [mailto:jacmet@gmail.com] On Behalf Of Peter
Korsgaard
> Sent: Wednesday, April 02, 2008 3:51 AM
> To: John Linn
> Cc: linuxppc-embedded@ozlabs.org; git
> Subject: Re: Virtex V5FX PPC 440 Support In Xilinx Git Tree
>=20
> >>>>> "John" =3D=3D John Linn <John.Linn@xilinx.com> writes:
>=20
>  John> I pushed PowerPC 440 support to the Xilinx Git server with
>  John> support for ppc arch and with powerpc arch support coming in
>  John> the near future.
>=20
> Neat, but why have you added arch/ppc support? It's supposed to go
> away pretty much by the time the hardware gets in the hand of
> developers.
>=20
> --
> Bye, Peter Korsgaard