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: Sat, 24 May 2008 11:28:23 +0200	[thread overview]
Message-ID: <1211621303.2763.9.camel@localhost.localdomain> (raw)

Thanks John. 

I should explain that I have only MPC8548 on the board. Other elements
with access via RapidIO will be on another board which is not connected
now. I guess that the common transport size does not matter in this case
because we do not have any communication.

Should I assume that the most probable reason of hung up i the mapping
of memory? The kernel hung up in function in_be32(regs_win + RIO_CCSR).
This is access to configuration register.

Thanks,
Adam

On Mon, 2008-05-19 at 09:22 +0100, John Traill wrote:
> Adam,
> 
> Make sure you have matching common transport sizes in your system -
Section 4.4.3.16 RapidIO System Size in the 8548 manual.
> 

             reply	other threads:[~2008-05-24  9:28 UTC|newest]

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

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=1211621303.2763.9.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.