From: Dmitriy Tochansky <toch@dfpost.ru>
To: linux-mips@linux-mips.org
Subject: mmap problem another :)
Date: Thu, 9 Dec 2004 16:12:07 +0300 [thread overview]
Message-ID: <20041209161207.39140f0d.toch@dfpost.ru> (raw)
Seems like I found problem.
Look ret = io_remap_page_range(start, offset, size, vma->vm_page_prot); remaps
from "offset" which I got from pci_resource_start (curdev, IOMEM0); its ok
from first board where it eq 0x40000000 but on second it 0x40002040
Then I'm reading from x = mmap (NULL, MMAP_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); with
shift 0x3C>>2 where I expect board register. But for second board x points to where?
0x40000000 or 0x40002040 or as I think remap_page_range or sonething realign offset to
PAGE so x points to 0x40002000 or 0x40003000 and reading with shift 0x3C have no sense.
Am I rigth?
next reply other threads:[~2004-12-09 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 13:12 Dmitriy Tochansky [this message]
2004-12-09 14:36 ` mmap problem another :) Dan Malek
2004-12-14 7:51 ` Dmitriy Tochansky
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 16:40 Dmitriy Tochansky
2004-12-08 17:27 ` Dan Malek
2004-12-08 18:20 ` Pete Popov
2004-12-09 6:56 ` Dmitriy Tochansky
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=20041209161207.39140f0d.toch@dfpost.ru \
--to=toch@dfpost.ru \
--cc=linux-mips@linux-mips.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