linux-kernel - Re: [PATCH 2.6.19-rc1 update4] drivers: add LCD support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45470DB8.5020906@innova-card.com>
Date:	Tue, 31 Oct 2006 09:47:52 +0100
From:	Franck Bui-Huu <vagabon.xyz@...il.com>
To:	Miguel Ojeda <maxextreme@...il.com>
CC:	Franck <vagabon.xyz@...il.com>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 update4] drivers: add LCD support

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 ?

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... ;)

bye
		Franck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/