linux-kernel - Re: [PATCH 2.6.19-rc1 full] 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: <4545BB3E.7030503@innova-card.com>
Date:	Mon, 30 Oct 2006 09:43:42 +0100
From:	Franck Bui-Huu <vagabon.xyz@...il.com>
To:	Miguel Ojeda <maxextreme@...il.com>
CC:	Franck Bui-Huu <vagabon.xyz@...il.com>, akpm@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.19-rc1 full] drivers: add LCD support

Miguel Ojeda wrote:
> 
> Sorry, I meant: You can't mmap a RAM address using functions like the
> usual remap_pfn_range (as such functions doesn't like physical RAM
> addresses, they want I/O ports for example, like 0x378). So, you can't
> use smem_start. You need to code your own mmap & nopage function. (It
> is explained in LDD3 very well).
> 

well I must admit that I don't understand why... I suppose you refered
to that section in ldd3:

	An interesting limitation of remap_pfn_range is that it gives
	access only to reserved pages and physical addresses above the
	top of physical memory.

I take a quick look at the implementation of remap_pfn_range() and
there's no such limitation I can see (fortunately).

		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/