linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Ed Goforth <egoforth@gmail.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: mmap on 440gx
Date: Thu, 16 Jun 2005 15:55:25 -0700	[thread overview]
Message-ID: <20050616155525.A4541@cox.net> (raw)
In-Reply-To: <75b39f0105061614333199ec37@mail.gmail.com>; from egoforth@gmail.com on Thu, Jun 16, 2005 at 05:33:44PM -0400

On Thu, Jun 16, 2005 at 05:33:44PM -0400, Ed Goforth wrote:
> I've been struggling with implementing mmap on a 440gx-based custom
> board.  I have been able to use ioremap(), but we really need a mmap()
> for our software.  The kernel is 2.4.18 (TimeSys 4.0).

There are some special things done for handling [io]_remap_page/pfn_range
on other vendor kernels and the current mainline kernel.  I'm not sure
if your vendor kernel addressed them since it would be a vendor-specific
patch in that timeframe.  The special things are due to 36-bit
addressing.

> I'm trying to access one of our FPGA's located at 0x50000000.  Offsets

Let's start at the beginning.  How do you have FPGA's at 0x50000000?
that address falls with the fix DDR SDRAM area on the 440GX memory
map. All peripheral and EBC space is mapped by 4GB. You lost me
right here. Oh wait, are you referring to the least significant 32-bits
of the physical mapping. It's not really at 0x50000000.

You need something like the bigphys_remap patch for 2.4 that can be
found at ftp://source.mvista.com/pub/linuxppc/

It does the same fixup for remap_page_range() that happens for
ioremap().  In 2.6 this stuff is all in the mainline kernel but
you use io_rename_[page|pfn]_range() there.

-Matt

  reply	other threads:[~2005-06-16 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 21:33 mmap on 440gx Ed Goforth
2005-06-16 22:55 ` Matt Porter [this message]
2005-06-17  3:47   ` Ed Goforth
2005-06-17  4:41     ` Matt Porter
2005-06-17  5:42       ` Ed Goforth
2005-06-17  7:24         ` Matt Porter

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=20050616155525.A4541@cox.net \
    --to=mporter@kernel.crashing.org \
    --cc=egoforth@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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).