From: "Miguel Ojeda" <maxextreme@gmail.com>
To: Franck <vagabon.xyz@gmail.com>
Cc: "Andrew Morton" <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 update4] drivers: add LCD support
Date: Tue, 31 Oct 2006 14:58:53 +0100 [thread overview]
Message-ID: <653402b90610310558o40898827id1fe2ea0e1f28c2a@mail.gmail.com> (raw)
In-Reply-To: <45470DB8.5020906@innova-card.com>
On 10/31/06, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
> Miguel Ojeda wrote:
> > Again: Please read LDD3. It explains it well. Read all the "Remapping
> > RAM" chapter and you will understand what I've done, or just try to
> > remap RAM yourself with remap_pfn_range.
>
> Well, I'm trying to get an explanation here and here is what I get
> from you:
>
> MO > LDD3 states it must work like this. (Note: it doesn't explain
> why though)
> FBH > Weird I read the implementation of remap_pfn_range() and it
> doesn't seem to have such restriction, I'm wondering how
> things work...
> MO > Again it's stated in LDD3, read again.
>
> Do you really think you explain anything with such replies ?
>
Do you really think I have to explain anything with my replies? I was
just trying to help you telling where I found the answer.
Anyway, isn't it explained in LDD3? isn't it stated in LDD3? I think
it is (yep, not deeply, but enough: other books cover that points
better and a device driver programmer doesn't have to know about
implementations, right?). Sure, neither the book or I didn't know
about the VM_PFNMAP change, but that doesn't change that I was trying
to encourage you to read such chapter, the same way I found the answer
there.
>
> Fortunately, Hugh Dickins gives a hint and it appears that the
> restriction doesn't hold anymore.
>
> > (I really tried it using
> > different ways and I couldn't map it with remap_pfn_range, it returns
> > you a place full with zeros, as LDD3 states).
>
> I'm really wondering how did you test the thing... ;)
>
And I still say I tried it, many ways, using remap_pfn_range() and
other weird things also. Finally, I thought something was wrong, so I
read LDD3 and I found the explanation about why my code mmap couldn't
mmap RAM. Also, my area was full of zeros, as LDD3 states. So I read a
little further and I did what "Remapping RAM" explains.
Anything else?
Bye,
Miguel Ojeda
next prev parent reply other threads:[~2006-10-31 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 17:48 Miguel Ojeda Sandonis
2006-10-27 5:07 ` Andrew Morton
2006-10-27 12:42 ` Miguel Ojeda
2006-10-30 9:35 ` Franck Bui-Huu
2006-10-30 13:53 ` Miguel Ojeda
2006-10-31 8:47 ` Franck Bui-Huu
2006-10-31 13:58 ` Miguel Ojeda [this message]
2006-10-30 14:24 ` Hugh Dickins
2006-10-27 15:34 Miguel Ojeda Sandonis
2006-10-31 8:13 ` Franck Bui-Huu
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=653402b90610310558o40898827id1fe2ea0e1f28c2a@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vagabon.xyz@gmail.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
all inboxes | Powered by JetHome®