[Buildroot] [PATCH 03/14] RESEND: handle MMU configuration

Peter Korsgaard jacmet at uclibc.org
Fri Oct 9 11:22:44 UTC 2009


>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com> writes:

 Thomas> Le Wed,  7 Oct 2009 23:27:47 +0200,
 Thomas> Bernhard Reutner-Fischer <rep.dot.nop at gmail.com> a écrit :

 >> +config BR2_HAVE_NOMMU
 >> +	def_bool n
 >> +	# assume that we have an MMU per default.

 Thomas> Maybe we should use BR2_HAVE_MMU, def_bool y. The
 Thomas> non-not-negative-if-not-options are really hard to understand.

I guess the idea is that the architectures can 'select' this option
behind the user's back. There's afaik nothing in kconfig to disable
another option if you enable something.

You could ofcourse move the logic here instead of in the individual arch
handling (E.G. default y if BR2_ARCH_bfin, or what it now is).

 >> +config BR2_USE_MMU
 >> +	bool "Use MMU"
 >> +	default y
 >> +	depends on !BR2_HAVE_NOMMU
 >> +	help
 >> +	  If your target has an MMU and you want to use it
 >> +	  then say Y here.

 Thomas> What's the usage of these two new options ?

Yes, I would like to know this as well. I would imagine properly
supporting nommu would take quite some more effort than this (E.G. most
packages should get hidden).

-- 
Bye, Peter Korsgaard



More information about the buildroot mailing list