From: Jie Zhang jie.zh...@analog.com
The no-mmu code currently clears all anonymous mmap-ed memory. While this
is what we want in the default case, all memory allocation from userspace
under no-mmu has to go through this interface, including malloc() which is
allowed to return uninitialized
On Tue, Oct 13, 2009 at 07:20:21AM -0400, Mike Frysinger wrote:
From: Jie Zhang jie.zh...@analog.com
The NOMMU code currently clears all anonymous mmapped memory. While this
is what we want in the default case, all memory allocation from userspace
under NOMMU has to go through this
On Mon, Oct 12, 2009 at 11:53:45AM +0100, Philip Nye wrote:
I am trying to build a system for Coldfire with an up-to-date kernel, tools
and library. I have the latest uClinux dist (patched to 20090810) and
Codesourcery tools 4.3-209. This refused to build with an error of limits.h
not found.
On Tue 13 Oct 2009 03:44, Mike Frysinger pondered:
From: Jie Zhang jie.zh...@analog.com
The no-mmu code currently clears all anonymous mmap-ed memory. While this
is what we want in the default case, all memory allocation from userspace
under no-mmu has to go through this interface,
Jivin Mike Frysinger lays it down ...
From: Jie Zhang jie.zh...@analog.com
The NOMMU code currently clears all anonymous mmapped memory. While this
is what we want in the default case, all memory allocation from userspace
under NOMMU has to go through this interface, including malloc()