From: Trevor Woerner <ppc339@vtnet.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: address translation
Date: Thu, 15 May 2003 23:13:13 -0400 [thread overview]
Message-ID: <200305152313.13244.ppc339@vtnet.ca> (raw)
In-Reply-To: <1052999180.1568.129.camel@hermes>
On May 15, 2003 07:46 am, Gary Thomas wrote:
> On Thu, 2003-05-15 at 05:29, Trevor Woerner wrote:
> > I want to setup a mapping so that when anything tries to read/write
> > the 16 bytes at 0x1f0 - 0x1ff the actual physical memory that gets
> > accessed is 0xf7000000 - 0xf700000f.
>
> Perhaps a specialized device driver would be a better choice.
Unfortunately, that seems to be the path I'm going down.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-16 3:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 11:29 address translation Trevor Woerner
2003-05-15 11:46 ` Gary Thomas
2003-05-16 3:13 ` Trevor Woerner [this message]
2003-05-15 12:13 ` Magnus Damm
2003-05-16 3:14 ` Trevor Woerner
2003-05-15 14:05 ` Benjamin Herrenschmidt
2003-05-16 4:02 ` Trevor Woerner
2003-05-16 8:35 ` Geert Uytterhoeven
2003-05-16 9:00 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 3:50 Trevor Woerner
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=200305152313.13244.ppc339@vtnet.ca \
--to=ppc339@vtnet.ca \
--cc=linuxppc-dev@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).