From: Dmitriy Tochansky <toch@dfpost.ru>
To: Dan Malek <dan@embeddededge.com>
Cc: linux-mips@linux-mips.org
Subject: Re: mmap problem another :)
Date: Thu, 9 Dec 2004 09:56:59 +0300 [thread overview]
Message-ID: <20041209095659.651b7a1d.toch@dfpost.ru> (raw)
In-Reply-To: <5FE01AB3-493E-11D9-81C3-003065F9B7DC@embeddededge.com>
On Wed, 8 Dec 2004 12:27:02 -0500
Dan Malek <dan@embeddededge.com> wrote:
>
> On Dec 8, 2004, at 11:40 AM, Dmitriy Tochansky wrote:
>
> > ret = remap_page_range_high (start, offset, size,
> > vma->vm_page_prot);
>
> Hmmm....this is in 2.4? Did you apply all of the 36-bit IO
> patch as Pete Popov has mentioned in past e-mail messages?
Could you please direct me where it is exectly? In this maillist? May be on the web?
> Did you make sure you enabled CONFIG_64BIT_PHYS_ADDR?
Yes. I'm sure.
next prev parent reply other threads:[~2004-12-09 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 16:40 mmap problem another :) Dmitriy Tochansky
2004-12-08 17:27 ` Dan Malek
2004-12-08 18:20 ` Pete Popov
2004-12-09 6:56 ` Dmitriy Tochansky [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 13:12 Dmitriy Tochansky
2004-12-09 14:36 ` Dan Malek
2004-12-14 7:51 ` 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=20041209095659.651b7a1d.toch@dfpost.ru \
--to=toch@dfpost.ru \
--cc=dan@embeddededge.com \
--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