From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adam Nowak <uboot@op.pl>
Date: Sun, 18 May 2008 22:22:31 +0200
Subject: [U-Boot-Users]  RapidIO on custom board (MPC8548 )
Message-ID: <1211142152.4365.28.camel@localhost.localdomain>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

I have to configure the system (u-boot, kernel) and create the RIO
driver. Could you advise me how to fix my current problem?

a) Kernel log:
...
Setting up RapidIO peer-to-peer network /soc8548 at e0000000/rapidi0
RIO: Of-device full name /soc8548 at e0000000/rapidio at c0000      
RIO: LAW start 0x00000000c0000000, size 0x0000000020000000.   
RIO: Regs start 0xe00c0000 size 0x00020000  
[there are not any next messages, the board hung up]

b) Corresponding Source Code
The kernel hung up in the file
linux-2.6.23/arch/powerpc/sysdev/fsl_rio.c
Function fsl_rio_setup() is executed but it hung on in_be32(regs_win +
RIO_CCSR);

c) u-boot configuration
#define	CONFIG_RIO 1
#define CFG_RIO_MEM_BASE 0xC0000000
#define CFG_RIO_MEM_SIZE 0x20000000 /* 512M */

d) Device Tree Source
 rapidio at c0000 {
  compatible = "fsl,rapidio-delta";
  #address-cells = <2>;
  #size-cells = <2>;
  reg = <c0000 20000>;
  ranges = <0 0 c0000000 20000000>;
  interrupt-parent = <&mpic>;
  interrupts = <30 2 31 2 32 2 35 2 36 2 37 2 38 2>;
 };

If you can not advise me on technical aspects, tell me please what I
should read to understand initialization of RIO in the kernel.

Thanks,
Adam