From: Paul Miller <pmiller9@users.sourceforge.net>
To: "Kevin A. Sapp" <Kevin.Sapp@catapult.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Peripherals Memory Mapping
Date: Sun, 14 Dec 2003 09:28:22 -0600 [thread overview]
Message-ID: <200312140928.23106.pmiller9@users.sourceforge.net> (raw)
In-Reply-To: <3FCB3969.9010707@catapult.com>
On Monday 01 December 2003 6:51 am, Kevin A. Sapp wrote:
> Hello,
>
> Maybe this is a simple question, but I have searched the code
> and played around with no luck. This is for an 8260 FADS
> board, later to be used on custom H/W.
>
> How and where do I add peripherals memory to the memory
> map? I have tried adding it in the ads_map_io function but
> when I try to access the 82xx internal memory space there to
> add the memory to the base and option registers it dies.
> io_block_mapping is called successfully for the internal
> space, but appears to be inaccessable at this time.
>
> Is there a function that adds memory ranges to both the Linux
> map and the processor map (Base and Option registers) ?
I recently jumped into the embedded linux world and I've been playing
around with a 405EP from Intrinsyc. In order to get I/O access to
the peripheral bus, you need to ioremap_nocache() the peripheral
memory in a kernel module, then mmap() it in user space. For the DCR
registers (e.g., the embedded memory controller (EBC) registers),
you'll need to modify these in kernel space by calling mtdcr() and
mfdcr().
I've been able to communicate with external hardware via peripheral I/
O. I noticed that memory addresses should lie on a 16 or 32-bit
boundary, otherwise the write pulse occurs too late for single
writes.
Hope this helps,
-Paul
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-14 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 16:07 mpc / linux kernel - user space Juergen Oberhofer
2003-11-27 17:38 ` Jaap-Jan Boor
2003-11-27 18:08 ` Juergen Oberhofer
2003-11-27 19:28 ` Dan Kegel
2003-11-28 4:30 ` How to change /proc to the writable directory John Zhou
2003-11-28 8:12 ` Wolfgang Denk
2003-11-28 9:16 ` mpc / linux kernel - user space Jaap-Jan Boor
2003-11-28 15:42 ` Dan Malek
2003-12-01 8:18 ` Jaap-Jan Boor
2003-12-01 12:51 ` Peripherals Memory Mapping Kevin A. Sapp
2003-12-14 15:28 ` Paul Miller [this message]
2003-12-01 13:47 ` mpc / linux kernel - user space Juergen Oberhofer
2003-11-28 5:34 ` Sampath Kumar
2003-11-28 8:14 ` Wolfgang Denk
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=200312140928.23106.pmiller9@users.sourceforge.net \
--to=pmiller9@users.sourceforge.net \
--cc=Kevin.Sapp@catapult.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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).