From: "Kevin A. Sapp" <Kevin.Sapp@catapult.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Peripherals Memory Mapping
Date: Mon, 01 Dec 2003 07:51:53 -0500 [thread overview]
Message-ID: <3FCB3969.9010707@catapult.com> (raw)
In-Reply-To: <1070266735.328.5.camel@linpc003.aimsys.nl>
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) ?
Thank you
Kevin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-01 12:51 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 ` Kevin A. Sapp [this message]
2003-12-14 15:28 ` Peripherals Memory Mapping Paul Miller
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=3FCB3969.9010707@catapult.com \
--to=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).