From: "Martin Schlemmer [c]" <azarah@nosferatu.za.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org, luc@saillard.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: rc4-mm1 and pwc-unofficial: kernel BUG and scheduling while atomic [u]
Date: Sun, 17 Oct 2004 21:57:45 +0200 [thread overview]
Message-ID: <1098043065.15115.13.camel@nosferatu.lan> (raw)
In-Reply-To: <20041017190054.GB5607@holomorphy.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Sun, 2004-10-17 at 12:00 -0700, William Lee Irwin III wrote:
> On Sun, 2004-10-17 at 02:30 -0700, William Lee Irwin III wrote:
> >> You need to right shift the argument by PAGE_SHIFT.
>
> On Sun, Oct 17, 2004 at 08:35:31PM +0200, Martin Schlemmer [c] wrote:
> > I am trying to get vesafb-tng to work with rc4-mm1, but are not sure
> > when to shift the argument by PAGE_SHIFT, and when not to. The patches
> > from you in rc4-mm1 sometimes shifts the second arg, other times the
> > third, and other times not at all. Is there a easy way for a mostly
> > clueless person to figure out when to shift what argument and when not?
>
> Please point out where these inconsistencies occur and I will repair
> them.
>
> Only the third argument changed, from a physical address to a pfn.
>
Its the vesafb-tng patch
(http://dev.gentoo.org/~spock/projects/vesafb-tng/)
Relevant part:
----
vma.vm_mm = current->active_mm;
vma.vm_page_prot.pgprot = PROT_READ | PROT_EXEC | PROT_WRITE;
ret = remap_page_range(&vma, 0x000000, __pa(mem), REAL_MEM_SIZE, vma.vm_page_prot);
ret += remap_page_range(&vma, 0x0a0000, 0x0a0000, 0x100000 - 0x0a0000, vma.vm_page_prot);
----
I did it as:
----
vma.vm_mm = current->active_mm;
vma.vm_page_prot.pgprot = PROT_READ | PROT_EXEC | PROT_WRITE;
ret = remap_pfn_range(&vma, 0x000000, __pa(mem) >> PAGE_SHIFT, REAL_MEM_SIZE, vma.vm_page_prot);
ret += remap_pfn_range(&vma, 0x0a0000, 0x0a0000, 0x100000 - 0x0a0000, vma.vm_page_prot);
----
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-17 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 7:36 rc4-mm1 and pwc-unofficial: kernel BUG and scheduling while atomic Norbert Preining
2004-10-17 9:30 ` William Lee Irwin III
2004-10-17 18:22 ` William Lee Irwin III
2004-10-17 18:35 ` rc4-mm1 and pwc-unofficial: kernel BUG and scheduling while atomic [u] Martin Schlemmer [c]
2004-10-17 19:00 ` William Lee Irwin III
2004-10-17 19:57 ` Martin Schlemmer [c] [this message]
2004-10-17 20:13 ` William Lee Irwin III
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=1098043065.15115.13.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc@saillard.org \
--cc=preining@logic.at \
--cc=wli@holomorphy.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