All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerhard Jaeger <g.jaeger@sysgo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Problem with OPB access on 440GX and Linux 2.6.15
Date: Mon, 9 Oct 2006 16:49:14 +0200	[thread overview]
Message-ID: <200610091649.14853.g.jaeger@sysgo.com> (raw)
In-Reply-To: <452A52B4.1010303@googlemail.com>

On Monday 09 October 2006 15:46, powerpc440 wrote:
> Hi everybody,
>=20
> I'm having a PPC440GX based board, based on Ocotea.
> On the board is a Xilinx CPLD chip, connected with OPB (On-Chip
> Peripheral Bus).
> Under U-Boot I can communicate =96 reading and writing, without any
> problems, but when the Linux kernel ones is loaded, then I'm getting
> error message: =93Bus error=94. This error message appears on reading or
> writing.
> How I can access the units, which are connected with OPB?
>=20
> There are the source code from the driver, that I use :
>=20
> static void io_addr =3D ioremap(0x48300000, 0x100000); /* allocate 1MB
> adress space */
> long value =3D readl(io_addr + 0x7000);
>=20
[SNIPSNAP]

Hi,

are you sure the address is correct?
This looks to me like the Ocotea FPGA address minus 0x100000000...
In that case use ioremap64().

HTH
Gerhard

=2D-=20
Gerhard Jaeger <gjaeger@sysgo.com>           =20
SYSGO AG                      Embedded and Real-Time Software
www.sysgo.com | www.elinos.com | www.pikeos.com | www.osek.de=20

  reply	other threads:[~2006-10-09 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 13:46 Problem with OPB access on 440GX and Linux 2.6.15 powerpc440
2006-10-09 14:49 ` Gerhard Jaeger [this message]
2006-10-09 15:21 ` Jeff Mock

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=200610091649.14853.g.jaeger@sysgo.com \
    --to=g.jaeger@sysgo.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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.