From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mmap question on ppc440
Date: Mon, 5 Nov 2007 15:16:59 -0600 [thread overview]
Message-ID: <20071105151659.3ea601e4@weaponx> (raw)
In-Reply-To: <472F8503.2080705@harris.com>
On Mon, 05 Nov 2007 16:02:59 -0500
"Steven A. Falco" <sfalco@harris.com> wrote:
> I am attempting to access the CPLD on the AMCC Sequoia board from
> user-land. I open /dev/mem, and mmap it, then try to access the
> resulting pointer. That works fine when accessing physical addresses
> that correspond to RAM, but as soon as I try to access the CPLD at
> physical address 0xc0000000, I get an infinite machine check.
That's because the CPLD is actually at physical address 0x1C0000000.
Yay for 36-bit physical addresses.
josh
next prev parent reply other threads:[~2007-11-05 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:02 mmap question on ppc440 Steven A. Falco
2007-11-05 21:16 ` Josh Boyer [this message]
2007-11-06 6:50 ` Stefan Roese
2007-11-06 22:02 ` Benjamin Herrenschmidt
2007-11-06 22:59 ` Josh Boyer
2007-11-06 23:31 ` Benjamin Herrenschmidt
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=20071105151659.3ea601e4@weaponx \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfalco@harris.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).