From: Frank Smith <smith@amirix.com>
To: Dan Malek <dan@netx4.com>
Cc: "Mark S. Mathews" <mark@absoval.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Can't mmap the top 1MB of /dev/mem?
Date: Thu, 22 Jun 2000 16:06:17 -0300 [thread overview]
Message-ID: <00Jun22.160620adt.7305@dragon.appliedmicro.ns.ca> (raw)
In-Reply-To: <39525D02.AA611102@embeddededge.com>
On Thu, 22 Jun 2000, Dan Malek wrote:
>
> Frank Smith wrote:
>
> > Wouldn't this account for it?
>
>
> No. Those are virtual address calculations in that file........
Oops. Upon thinking about this a bit more, the problem we were having
was that we were trying to get physical 0xfe000000 mapped to virtual
0xfe000000.
The board we're using has firmware that we want to be able to call
after Linux is up and running. The FW runs from 0x3000-0x60000, but
refers to data up in 0xfe space. Our first naive attempts were to
use mmap from userland, but we ended up putting stuff in the kernel
and mapping flash directly with remap_page_range().
Frank.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-22 19:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-22 17:15 Can't mmap the top 1MB of /dev/mem? Mark S. Mathews
2000-06-22 17:43 ` Dan Malek
2000-06-22 18:47 ` Pavel Roskin
2000-06-22 18:54 ` Dan Malek
2000-06-22 19:58 ` Pavel Roskin
2000-06-22 21:46 ` Dan Malek
2000-06-22 19:00 ` Mark S. Mathews
2000-06-22 19:37 ` Pavel Roskin
2000-06-22 19:50 ` Mark S. Mathews
2000-06-22 20:24 ` Pavel Roskin
2000-06-22 17:50 ` Pavel Roskin
2000-06-22 18:14 ` Frank Smith
2000-06-22 18:37 ` Dan Malek
2000-06-22 19:06 ` Frank Smith [this message]
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=00Jun22.160620adt.7305@dragon.appliedmicro.ns.ca \
--to=smith@amirix.com \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mark@absoval.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).