All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Nowak <uboot@op.pl>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users]  RapidIO on custom board (MPC8548 )
Date: Sun, 18 May 2008 22:22:31 +0200	[thread overview]
Message-ID: <1211142152.4365.28.camel@localhost.localdomain> (raw)

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

             reply	other threads:[~2008-05-18 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18 20:22 Adam Nowak [this message]
2008-05-19  8:22 ` [U-Boot-Users] RapidIO on custom board (MPC8548 ) John Traill
  -- strict thread matches above, loose matches on Subject: below --
2008-05-24  9:28 Adam Nowak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1211142152.4365.28.camel@localhost.localdomain \
    --to=uboot@op.pl \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.