On 10/02/2011 05:01 AM, Mike Frysinger wrote:
On Thursday, September 29, 2011 18:40:23 Steve Bennett wrote:
--- a/extra/Configs/Config.microblaze
+++ b/extra/Configs/Config.microblaze
+choice
+ prompt "Microblaze MMU Capability"
+ default CONFIG_MICROBLAZE_NO_MMU
+ depends on TARGET_microblaze
+ help
+ Determines the MMU capability of your microblaze CPU.
+
+config CONFIG_MICROBLAZE_NO_MMU
+ bool "no mmu"
+ select HAVE_NO_PIC
+ select ARCH_HAS_NO_SHARED
select ARCH_HAS_NO_MMU
+
+config CONFIG_MICROBLAZE_MMU
+ bool "mmu"
+ select ARCH_HAS_MMU
+
+endchoice
why do you need your own ? we already have common ARCH_USE_MMU.
The reason behind not using ARCH_USE_MMU is that the
Microblaze core may not necessarily have a MMU. (The
MMU is an optional feature of the core).
The configuration is based on how the ARM architecture
uses the target processor choice in extra/Configs/Config.arm
for the various MMU/no-MMU processors.
If there's a better way to work with this, let me know and
I'll change it to suit.
ryan
_______________________________________________
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc
