From: Anand Gurumurthy <anand@rttsindia.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Problem with mmap( ) in linux ppc!
Date: Mon, 10 Mar 2003 11:50:59 +0530 [thread overview]
Message-ID: <20030310115059.2862dfb1.anand@rttsindia.com> (raw)
Hi,
We have a driver for a communication card which has memory mapped IO.We are using redhat 2.2.14 kernel on intel p3 processor. The driver has an mmap entry point to map device memory into the user space using remap_page_range(). It works fine with intel P3. When we try to use the same driver with ppc linux 2.2.17 kernel, the mmap system call does not map the proper device memory.Is there anything extra required for using mmap with ppc? Please help me with your suggestions.
Thanks,
Anand Gurumurthy.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next reply other threads:[~2003-03-10 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 6:20 Anand Gurumurthy [this message]
2003-03-10 8:48 ` Benjamin Herrenschmidt
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=20030310115059.2862dfb1.anand@rttsindia.com \
--to=anand@rttsindia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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