1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/config/kernel/linux.in.2 Wed Apr 27 22:37:32 2011 +0200
1.3 @@ -0,0 +1,232 @@
1.4 +# Linux kernel options
1.5 +
1.6 +choice
1.7 + bool
1.8 + prompt "Get kernel headers from:"
1.9 +
1.10 +config KERNEL_LINUX_INSTALL
1.11 + bool
1.12 + prompt "kernel's 'headers_install'"
1.13 + help
1.14 + This will make use of the new headers_install rule in recent kernels.
1.15 + This is most probably what you want to use.
1.16 +
1.17 +config KERNEL_LINUX_USE_CUSTOM_HEADERS
1.18 + bool
1.19 + prompt "pre-installed headers tree"
1.20 + help
1.21 + If you have some pre-installed kernel headers lying around, you can
1.22 + enter the path to these headers, below, they will be copied from
1.23 + there, and into the toolchain's sysroot.
1.24 +
1.25 + Note:
1.26 + This will *not* let you use a complete kernel tree!
1.27 + If you want to use your own full kernel tree, then you want to
1.28 + say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
1.29 +
1.30 +endchoice
1.31 +
1.32 +if KERNEL_LINUX_INSTALL
1.33 +
1.34 +choice
1.35 + bool
1.36 + prompt "Linux kernel version"
1.37 +# Don't remove next line
1.38 +# CT_INSERT_VERSION_BELOW
1.39 +
1.40 +config KERNEL_V_2_6_38_3
1.41 + bool
1.42 + prompt "2.6.38.3"
1.43 +
1.44 +config KERNEL_V_2_6_38_2
1.45 + bool
1.46 + prompt "2.6.38.2"
1.47 +
1.48 +config KERNEL_V_2_6_38_1
1.49 + bool
1.50 + prompt "2.6.38.1"
1.51 +
1.52 +config KERNEL_V_2_6_38
1.53 + bool
1.54 + prompt "2.6.38"
1.55 +
1.56 +config KERNEL_V_2_6_37_6
1.57 + bool
1.58 + prompt "2.6.37.6"
1.59 +
1.60 +config KERNEL_V_2_6_36_4
1.61 + bool
1.62 + prompt "2.6.36.4"
1.63 +
1.64 +config KERNEL_V_2_6_35_12
1.65 + bool
1.66 + prompt "2.6.35.12 (longterm)"
1.67 + help
1.68 + The Linux 2.6.35 tree is a "longterm" maintenance branch.
1.69 +
1.70 + It is intended to fill the niche for users who are not using distribution
1.71 + kernels but want to use a regression-free kernel for a longer time.
1.72 +
1.73 + Critical bug fixes to later 2.6 releases are often ported to this branch
1.74 + which makes 2.6.35 a very useful base for many embedded developers seeking
1.75 + stable APIs or those who do not need the latest bleeding edge features.
1.76 +
1.77 + ... and no, this kernel has not undergone any specific QA testing.
1.78 +
1.79 + See the original announcement by Andi Kleen in the following mailing
1.80 + list entry:
1.81 + http://marc.info/?l=linux-kernel&m=129136895415202&w=4
1.82 +
1.83 +config KERNEL_V_2_6_34_8
1.84 + bool
1.85 + prompt "2.6.34.8"
1.86 +
1.87 +config KERNEL_V_2_6_33_11
1.88 + bool
1.89 + prompt "2.6.33.11"
1.90 +
1.91 +config KERNEL_V_2_6_32_38
1.92 + bool
1.93 + prompt "2.6.32.38 (longterm)"
1.94 + help
1.95 + The Linux 2.6.32 tree is a "longterm" maintenance branch.
1.96 +
1.97 + It is intended to fill the niche for users who are not using distribution
1.98 + kernels but want to use a regression-free kernel for a longer time.
1.99 +
1.100 + Critical bug fixes to later 2.6 releases are often ported to this branch
1.101 + which makes 2.6.32 a very useful base for many embedded developers seeking
1.102 + stable APIs or those who do not need the latest bleeding edge features.
1.103 +
1.104 + ... and no, this kernel has not undergone any specific QA testing.
1.105 +
1.106 + See the original announcement by Greg Kroah-Hartman in the following
1.107 + mailing list entry:
1.108 + http://marc.info/?l=linux-kernel&m=126384198403392&w=4
1.109 +
1.110 +config KERNEL_V_2_6_31_14
1.111 + bool
1.112 + prompt "2.6.31.14"
1.113 +
1.114 +config KERNEL_V_2_6_27_58
1.115 + bool
1.116 + prompt "2.6.27.58 (longterm)"
1.117 + help
1.118 + The Linux 2.6.27 tree is a "longterm" maintenance branch.
1.119 +
1.120 + It is intended to fill the niche for users who are not using distribution
1.121 + kernels but want to use a regression-free kernel for a longer time.
1.122 +
1.123 + Critical bug fixes to later 2.6 releases are often ported to this branch
1.124 + which makes 2.6.27 a very useful base for many embedded developers seeking
1.125 + stable APIs or those who do not need the latest bleeding edge features.
1.126 +
1.127 + ... and no, this kernel has not undergone any specific QA testing.
1.128 +
1.129 + See the original announcement by Adrian Bunk in the following mailing list
1.130 + entry:
1.131 + http://marc.info/?l=linux-kernel&m=122375909403298&w=4
1.132 +
1.133 + It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
1.134 + http://marc.info/?l=linux-kernel&m=129133701916793&w=4
1.135 +
1.136 +config KERNEL_LINUX_CUSTOM
1.137 + bool
1.138 + prompt "custom tarball"
1.139 + help
1.140 + Use a local tarball of a complete kernel source tree.
1.141 +
1.142 +config KERNEL_LINUX_CUSTOM_TARBALL
1.143 + string
1.144 + prompt "Path to custom tarball"
1.145 + depends on KERNEL_LINUX_CUSTOM
1.146 + help
1.147 + Enter here the path to the tarball of your full kernel tree.
1.148 +
1.149 +endchoice
1.150 +
1.151 +config KERNEL_VERSION
1.152 + string
1.153 +# Don't remove next line
1.154 +# CT_INSERT_VERSION_STRING_BELOW
1.155 + default "2.6.38.3" if KERNEL_V_2_6_38_3
1.156 + default "2.6.38.2" if KERNEL_V_2_6_38_2
1.157 + default "2.6.38.1" if KERNEL_V_2_6_38_1
1.158 + default "2.6.38" if KERNEL_V_2_6_38
1.159 + default "2.6.37.6" if KERNEL_V_2_6_37_6
1.160 + default "2.6.36.4" if KERNEL_V_2_6_36_4
1.161 + default "2.6.35.12" if KERNEL_V_2_6_35_12
1.162 + default "2.6.34.8" if KERNEL_V_2_6_34_8
1.163 + default "2.6.33.11" if KERNEL_V_2_6_33_11
1.164 + default "2.6.32.38" if KERNEL_V_2_6_32_38
1.165 + default "2.6.31.14" if KERNEL_V_2_6_31_14
1.166 + default "2.6.27.58" if KERNEL_V_2_6_27_58
1.167 +
1.168 +choice
1.169 + bool
1.170 + prompt "Kernel verbosity:"
1.171 + default KERNEL_LINUX_VERBOSITY_0
1.172 +
1.173 +config KERNEL_LINUX_VERBOSITY_0
1.174 + bool
1.175 + prompt "Simplified"
1.176 + help
1.177 + Print simplified command lines.
1.178 +
1.179 +config KERNEL_LINUX_VERBOSITY_1
1.180 + bool
1.181 + prompt "Full commands"
1.182 + help
1.183 + Print full command lines.
1.184 +
1.185 +config KERNEL_LINUX_VERBOSITY_2
1.186 + bool
1.187 + prompt "Exec reasons"
1.188 + help
1.189 + Print the reasons why a make target is rebuild.
1.190 +
1.191 +endchoice
1.192 +
1.193 +config KERNEL_LINUX_VERBOSE_LEVEL
1.194 + int
1.195 + default 0 if KERNEL_LINUX_VERBOSITY_0
1.196 + default 1 if KERNEL_LINUX_VERBOSITY_1
1.197 + default 2 if KERNEL_LINUX_VERBOSITY_2
1.198 +
1.199 +config KERNEL_LINUX_INSTALL_CHECK
1.200 + bool
1.201 + prompt "Check installed headers"
1.202 + default y
1.203 + help
1.204 + If you are in doubt that installed headers are buggy, say 'Y'
1.205 + here to have an extra check passed onto the headers.
1.206 +
1.207 +endif # KERNEL_LINUX_INSTALL
1.208 +
1.209 +if KERNEL_LINUX_USE_CUSTOM_HEADERS
1.210 +
1.211 +config KERNEL_LINUX_CUSTOM_IS_TARBALL
1.212 + bool
1.213 + prompt "This is a tarball"
1.214 + default n
1.215 + help
1.216 + If you say 'n' here, the path below is expected to point to a directory
1.217 + containing readily prepared headers
1.218 +
1.219 + If you say 'y' here, then the path below is expected to point to a
1.220 + tarball of such a directory.
1.221 +
1.222 + Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
1.223 + say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
1.224 +
1.225 + Now, passing a tarball around is easier than passing a directory, so
1.226 + if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
1.227 + say 'y' here, and enter the path to this tarball below.
1.228 +
1.229 +config KERNEL_LINUX_CUSTOM_PATH
1.230 + string
1.231 + prompt "Path to custom headers directory/tarball"
1.232 + help
1.233 + See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
1.234 +
1.235 +endif # KERNEL_LINUX_USE_CUSTOM_HEADERS