lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1181689112.9736.29.camel@pterry-fc6.micromemory.com>
Date:	Tue, 12 Jun 2007 15:58:32 -0700
From:	Phil Terry <pterry@...romemory.com>
To:	wei.zhang@...escale.com
Cc:	mporter@...nel.crashing.org, linuxppc-dev@...abs.org,
	paulus@...ba.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] Add RapidIO sector to MPC8641HPCN board dts file.

On Tue, 2007-06-12 at 17:02 +0800, Zhang Wei wrote:
> Add RapidIO sector to the MPC8641HPCN board dts file.
> 
> Signed-off-by: Zhang Wei <wei.zhang@...escale.com>
> ---
>  arch/powerpc/boot/dts/mpc8641_hpcn.dts |   13 +++++++++++++
>  1 files changed, 13 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/powerpc/boot/dts/mpc8641_hpcn.dts b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> index 04626b1..e2ce06e 100644
> --- a/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> +++ b/arch/powerpc/boot/dts/mpc8641_hpcn.dts
> @@ -329,6 +329,19 @@
>  				>;
>  		};
>  
> +		srio@...00 {
> +			device_type = "rapidio";
> +			compatible = "fsl,rapidio-v1.0";
> +			#address-cells = <2>;
> +			reg = <c0000 20000>;
> +			ranges = <0 0 c0000000 20000000>;

Don't understand the range setup... The code uses c0000000 as the start
and 20000000 as the size for the rapidio law. So whats the 0 0 for? 
At first I thought address-cells 2 means that the range numbers are
pairs expressing 64-bit numbers, eg start 0 0, size c0000000 20000000
but thats not right...

Sorry if I'm asking stupid questions....

And thanks for the patch, just what I need.

BTW do you have any notes/documentation on the space allocation routines
intended use. I'm trying to work it out but I don't see any actual users
of it yet... I need something like it for my distributed DMA driver,
hence the interest.

Cheers
Phil

> +			interrupt-parent = <&mpic>;
> +			/* err_irq bell_outb_irq bell_inb_irq
> +						msg1_tx_irq msg1_rx_irq
> +						msg2_tx_irq msg2_rx_irq */
> +			interrupts = <30 2 31 2 32 2 35 2 36 2 37 2 38 2>;
> +		};
> +
>  		mpic: pic@...00 {
>  			clock-frequency = <0>;
>  			interrupt-controller;


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ