MMU is the Memory Management Unit and the ARM inside GP32 relies a lot on it. Basic operations MMU does are: address translation between virtual and physical addresses, and protection & caching control of memory areas.
reason I ask is because I want to port the dlopen suite of functions from uCLibc. These support ARM processors, but only with MMU. They also need a malloc type function, which I guess is why they need an MMU.
reason I ask is because I want to port the dlopen suite of functions from uCLibc. These support ARM processors, but only with MMU. They also need a malloc type function, which I guess is why they need an MMU.
Why would a libc required MMU support? Weren't uclibc originally just targetted to MMUless systems? Oh... shared libraries might need that MMU support.
Does uClibc support shared libraries?
Yes. uClibc has native shared library support on i386, ARM, mips, SH, CRIS, and PowerPC processors. Other architectures can use shared libraries but will need to use the GNU libc shared library loader.
Shared Libraries are not currently supported by uClibc on MMU-less systems. SnapGear has implemented shared library support for MMU-less systems, however, so if you need MMU-less shared library support they may be able to help.