1.1 --- a/config/kernel/linux.in Wed Apr 27 22:18:07 2011 +0200
1.2 +++ b/config/kernel/linux.in Wed Apr 27 22:37:32 2011 +0200
1.3 @@ -4,234 +4,3 @@
1.4 select KERNEL_SUPPORTS_SHARED_LIBS
1.5 help
1.6 Build a toolchain targeting systems running Linux as a kernel.
1.7 -
1.8 -choice
1.9 - bool
1.10 - prompt "Get kernel headers from:"
1.11 -
1.12 -config KERNEL_LINUX_INSTALL
1.13 - bool
1.14 - prompt "kernel's 'headers_install'"
1.15 - help
1.16 - This will make use of the new headers_install rule in recent kernels.
1.17 - This is most probably what you want to use.
1.18 -
1.19 -if KERNEL_LINUX_INSTALL
1.20 -
1.21 -choice
1.22 - bool
1.23 - prompt "Linux kernel version"
1.24 -# Don't remove next line
1.25 -# CT_INSERT_VERSION_BELOW
1.26 -
1.27 -config KERNEL_V_2_6_38_3
1.28 - bool
1.29 - prompt "2.6.38.3"
1.30 -
1.31 -config KERNEL_V_2_6_38_2
1.32 - bool
1.33 - prompt "2.6.38.2"
1.34 -
1.35 -config KERNEL_V_2_6_38_1
1.36 - bool
1.37 - prompt "2.6.38.1"
1.38 -
1.39 -config KERNEL_V_2_6_38
1.40 - bool
1.41 - prompt "2.6.38"
1.42 -
1.43 -config KERNEL_V_2_6_37_6
1.44 - bool
1.45 - prompt "2.6.37.6"
1.46 -
1.47 -config KERNEL_V_2_6_36_4
1.48 - bool
1.49 - prompt "2.6.36.4"
1.50 -
1.51 -config KERNEL_V_2_6_35_12
1.52 - bool
1.53 - prompt "2.6.35.12 (longterm)"
1.54 - help
1.55 - The Linux 2.6.35 tree is a "longterm" maintenance branch.
1.56 -
1.57 - It is intended to fill the niche for users who are not using distribution
1.58 - kernels but want to use a regression-free kernel for a longer time.
1.59 -
1.60 - Critical bug fixes to later 2.6 releases are often ported to this branch
1.61 - which makes 2.6.35 a very useful base for many embedded developers seeking
1.62 - stable APIs or those who do not need the latest bleeding edge features.
1.63 -
1.64 - ... and no, this kernel has not undergone any specific QA testing.
1.65 -
1.66 - See the original announcement by Andi Kleen in the following mailing
1.67 - list entry:
1.68 - http://marc.info/?l=linux-kernel&m=129136895415202&w=4
1.69 -
1.70 -config KERNEL_V_2_6_34_8
1.71 - bool
1.72 - prompt "2.6.34.8"
1.73 -
1.74 -config KERNEL_V_2_6_33_11
1.75 - bool
1.76 - prompt "2.6.33.11"
1.77 -
1.78 -config KERNEL_V_2_6_32_38
1.79 - bool
1.80 - prompt "2.6.32.38 (longterm)"
1.81 - help
1.82 - The Linux 2.6.32 tree is a "longterm" maintenance branch.
1.83 -
1.84 - It is intended to fill the niche for users who are not using distribution
1.85 - kernels but want to use a regression-free kernel for a longer time.
1.86 -
1.87 - Critical bug fixes to later 2.6 releases are often ported to this branch
1.88 - which makes 2.6.32 a very useful base for many embedded developers seeking
1.89 - stable APIs or those who do not need the latest bleeding edge features.
1.90 -
1.91 - ... and no, this kernel has not undergone any specific QA testing.
1.92 -
1.93 - See the original announcement by Greg Kroah-Hartman in the following
1.94 - mailing list entry:
1.95 - http://marc.info/?l=linux-kernel&m=126384198403392&w=4
1.96 -
1.97 -config KERNEL_V_2_6_31_14
1.98 - bool
1.99 - prompt "2.6.31.14"
1.100 -
1.101 -config KERNEL_V_2_6_27_58
1.102 - bool
1.103 - prompt "2.6.27.58 (longterm)"
1.104 - help
1.105 - The Linux 2.6.27 tree is a "longterm" maintenance branch.
1.106 -
1.107 - It is intended to fill the niche for users who are not using distribution
1.108 - kernels but want to use a regression-free kernel for a longer time.
1.109 -
1.110 - Critical bug fixes to later 2.6 releases are often ported to this branch
1.111 - which makes 2.6.27 a very useful base for many embedded developers seeking
1.112 - stable APIs or those who do not need the latest bleeding edge features.
1.113 -
1.114 - ... and no, this kernel has not undergone any specific QA testing.
1.115 -
1.116 - See the original announcement by Adrian Bunk in the following mailing list
1.117 - entry:
1.118 - http://marc.info/?l=linux-kernel&m=122375909403298&w=4
1.119 -
1.120 - It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
1.121 - http://marc.info/?l=linux-kernel&m=129133701916793&w=4
1.122 -
1.123 -config KERNEL_LINUX_CUSTOM
1.124 - bool
1.125 - prompt "custom tarball"
1.126 - help
1.127 - Use a local tarball of a complete kernel source tree.
1.128 -
1.129 -config KERNEL_LINUX_CUSTOM_TARBALL
1.130 - string
1.131 - prompt "Path to custom tarball"
1.132 - depends on KERNEL_LINUX_CUSTOM
1.133 - help
1.134 - Enter here the path to the tarball of your full kernel tree.
1.135 -
1.136 -endchoice
1.137 -
1.138 -config KERNEL_VERSION
1.139 - string
1.140 -# Don't remove next line
1.141 -# CT_INSERT_VERSION_STRING_BELOW
1.142 - default "2.6.38.3" if KERNEL_V_2_6_38_3
1.143 - default "2.6.38.2" if KERNEL_V_2_6_38_2
1.144 - default "2.6.38.1" if KERNEL_V_2_6_38_1
1.145 - default "2.6.38" if KERNEL_V_2_6_38
1.146 - default "2.6.37.6" if KERNEL_V_2_6_37_6
1.147 - default "2.6.36.4" if KERNEL_V_2_6_36_4
1.148 - default "2.6.35.12" if KERNEL_V_2_6_35_12
1.149 - default "2.6.34.8" if KERNEL_V_2_6_34_8
1.150 - default "2.6.33.11" if KERNEL_V_2_6_33_11
1.151 - default "2.6.32.38" if KERNEL_V_2_6_32_38
1.152 - default "2.6.31.14" if KERNEL_V_2_6_31_14
1.153 - default "2.6.27.58" if KERNEL_V_2_6_27_58
1.154 -
1.155 -choice
1.156 - bool
1.157 - prompt "Kernel verbosity:"
1.158 - default KERNEL_LINUX_VERBOSITY_0
1.159 -
1.160 -config KERNEL_LINUX_VERBOSITY_0
1.161 - bool
1.162 - prompt "Simplified"
1.163 - help
1.164 - Print simplified command lines.
1.165 -
1.166 -config KERNEL_LINUX_VERBOSITY_1
1.167 - bool
1.168 - prompt "Full commands"
1.169 - help
1.170 - Print full command lines.
1.171 -
1.172 -config KERNEL_LINUX_VERBOSITY_2
1.173 - bool
1.174 - prompt "Exec reasons"
1.175 - help
1.176 - Print the reasons why a make target is rebuild.
1.177 -
1.178 -endchoice
1.179 -
1.180 -config KERNEL_LINUX_VERBOSE_LEVEL
1.181 - int
1.182 - default 0 if KERNEL_LINUX_VERBOSITY_0
1.183 - default 1 if KERNEL_LINUX_VERBOSITY_1
1.184 - default 2 if KERNEL_LINUX_VERBOSITY_2
1.185 -
1.186 -config KERNEL_LINUX_INSTALL_CHECK
1.187 - bool
1.188 - prompt "Check installed headers"
1.189 - default y
1.190 - help
1.191 - If you are in doubt that installed headers are buggy, say 'Y'
1.192 - here to have an extra check passed onto the headers.
1.193 -
1.194 -endif # KERNEL_LINUX_INSTALL
1.195 -
1.196 -config KERNEL_LINUX_USE_CUSTOM_HEADERS
1.197 - bool
1.198 - prompt "pre-installed headers tree"
1.199 - help
1.200 - If you have some pre-installed kernel headers lying around, you can
1.201 - enter the path to these headers, below, they will be copied from
1.202 - there, and into the toolchain's sysroot.
1.203 -
1.204 - Note:
1.205 - This will *not* let you use a complete kernel tree!
1.206 - If you want to use your own full kernel tree, then you want to
1.207 - say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
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
1.236 -
1.237 -endchoice
2.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
2.2 +++ b/config/kernel/linux.in.2 Wed Apr 27 22:37:32 2011 +0200
2.3 @@ -0,0 +1,232 @@
2.4 +# Linux kernel options
2.5 +
2.6 +choice
2.7 + bool
2.8 + prompt "Get kernel headers from:"
2.9 +
2.10 +config KERNEL_LINUX_INSTALL
2.11 + bool
2.12 + prompt "kernel's 'headers_install'"
2.13 + help
2.14 + This will make use of the new headers_install rule in recent kernels.
2.15 + This is most probably what you want to use.
2.16 +
2.17 +config KERNEL_LINUX_USE_CUSTOM_HEADERS
2.18 + bool
2.19 + prompt "pre-installed headers tree"
2.20 + help
2.21 + If you have some pre-installed kernel headers lying around, you can
2.22 + enter the path to these headers, below, they will be copied from
2.23 + there, and into the toolchain's sysroot.
2.24 +
2.25 + Note:
2.26 + This will *not* let you use a complete kernel tree!
2.27 + If you want to use your own full kernel tree, then you want to
2.28 + say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.
2.29 +
2.30 +endchoice
2.31 +
2.32 +if KERNEL_LINUX_INSTALL
2.33 +
2.34 +choice
2.35 + bool
2.36 + prompt "Linux kernel version"
2.37 +# Don't remove next line
2.38 +# CT_INSERT_VERSION_BELOW
2.39 +
2.40 +config KERNEL_V_2_6_38_3
2.41 + bool
2.42 + prompt "2.6.38.3"
2.43 +
2.44 +config KERNEL_V_2_6_38_2
2.45 + bool
2.46 + prompt "2.6.38.2"
2.47 +
2.48 +config KERNEL_V_2_6_38_1
2.49 + bool
2.50 + prompt "2.6.38.1"
2.51 +
2.52 +config KERNEL_V_2_6_38
2.53 + bool
2.54 + prompt "2.6.38"
2.55 +
2.56 +config KERNEL_V_2_6_37_6
2.57 + bool
2.58 + prompt "2.6.37.6"
2.59 +
2.60 +config KERNEL_V_2_6_36_4
2.61 + bool
2.62 + prompt "2.6.36.4"
2.63 +
2.64 +config KERNEL_V_2_6_35_12
2.65 + bool
2.66 + prompt "2.6.35.12 (longterm)"
2.67 + help
2.68 + The Linux 2.6.35 tree is a "longterm" maintenance branch.
2.69 +
2.70 + It is intended to fill the niche for users who are not using distribution
2.71 + kernels but want to use a regression-free kernel for a longer time.
2.72 +
2.73 + Critical bug fixes to later 2.6 releases are often ported to this branch
2.74 + which makes 2.6.35 a very useful base for many embedded developers seeking
2.75 + stable APIs or those who do not need the latest bleeding edge features.
2.76 +
2.77 + ... and no, this kernel has not undergone any specific QA testing.
2.78 +
2.79 + See the original announcement by Andi Kleen in the following mailing
2.80 + list entry:
2.81 + http://marc.info/?l=linux-kernel&m=129136895415202&w=4
2.82 +
2.83 +config KERNEL_V_2_6_34_8
2.84 + bool
2.85 + prompt "2.6.34.8"
2.86 +
2.87 +config KERNEL_V_2_6_33_11
2.88 + bool
2.89 + prompt "2.6.33.11"
2.90 +
2.91 +config KERNEL_V_2_6_32_38
2.92 + bool
2.93 + prompt "2.6.32.38 (longterm)"
2.94 + help
2.95 + The Linux 2.6.32 tree is a "longterm" maintenance branch.
2.96 +
2.97 + It is intended to fill the niche for users who are not using distribution
2.98 + kernels but want to use a regression-free kernel for a longer time.
2.99 +
2.100 + Critical bug fixes to later 2.6 releases are often ported to this branch
2.101 + which makes 2.6.32 a very useful base for many embedded developers seeking
2.102 + stable APIs or those who do not need the latest bleeding edge features.
2.103 +
2.104 + ... and no, this kernel has not undergone any specific QA testing.
2.105 +
2.106 + See the original announcement by Greg Kroah-Hartman in the following
2.107 + mailing list entry:
2.108 + http://marc.info/?l=linux-kernel&m=126384198403392&w=4
2.109 +
2.110 +config KERNEL_V_2_6_31_14
2.111 + bool
2.112 + prompt "2.6.31.14"
2.113 +
2.114 +config KERNEL_V_2_6_27_58
2.115 + bool
2.116 + prompt "2.6.27.58 (longterm)"
2.117 + help
2.118 + The Linux 2.6.27 tree is a "longterm" maintenance branch.
2.119 +
2.120 + It is intended to fill the niche for users who are not using distribution
2.121 + kernels but want to use a regression-free kernel for a longer time.
2.122 +
2.123 + Critical bug fixes to later 2.6 releases are often ported to this branch
2.124 + which makes 2.6.27 a very useful base for many embedded developers seeking
2.125 + stable APIs or those who do not need the latest bleeding edge features.
2.126 +
2.127 + ... and no, this kernel has not undergone any specific QA testing.
2.128 +
2.129 + See the original announcement by Adrian Bunk in the following mailing list
2.130 + entry:
2.131 + http://marc.info/?l=linux-kernel&m=122375909403298&w=4
2.132 +
2.133 + It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
2.134 + http://marc.info/?l=linux-kernel&m=129133701916793&w=4
2.135 +
2.136 +config KERNEL_LINUX_CUSTOM
2.137 + bool
2.138 + prompt "custom tarball"
2.139 + help
2.140 + Use a local tarball of a complete kernel source tree.
2.141 +
2.142 +config KERNEL_LINUX_CUSTOM_TARBALL
2.143 + string
2.144 + prompt "Path to custom tarball"
2.145 + depends on KERNEL_LINUX_CUSTOM
2.146 + help
2.147 + Enter here the path to the tarball of your full kernel tree.
2.148 +
2.149 +endchoice
2.150 +
2.151 +config KERNEL_VERSION
2.152 + string
2.153 +# Don't remove next line
2.154 +# CT_INSERT_VERSION_STRING_BELOW
2.155 + default "2.6.38.3" if KERNEL_V_2_6_38_3
2.156 + default "2.6.38.2" if KERNEL_V_2_6_38_2
2.157 + default "2.6.38.1" if KERNEL_V_2_6_38_1
2.158 + default "2.6.38" if KERNEL_V_2_6_38
2.159 + default "2.6.37.6" if KERNEL_V_2_6_37_6
2.160 + default "2.6.36.4" if KERNEL_V_2_6_36_4
2.161 + default "2.6.35.12" if KERNEL_V_2_6_35_12
2.162 + default "2.6.34.8" if KERNEL_V_2_6_34_8
2.163 + default "2.6.33.11" if KERNEL_V_2_6_33_11
2.164 + default "2.6.32.38" if KERNEL_V_2_6_32_38
2.165 + default "2.6.31.14" if KERNEL_V_2_6_31_14
2.166 + default "2.6.27.58" if KERNEL_V_2_6_27_58
2.167 +
2.168 +choice
2.169 + bool
2.170 + prompt "Kernel verbosity:"
2.171 + default KERNEL_LINUX_VERBOSITY_0
2.172 +
2.173 +config KERNEL_LINUX_VERBOSITY_0
2.174 + bool
2.175 + prompt "Simplified"
2.176 + help
2.177 + Print simplified command lines.
2.178 +
2.179 +config KERNEL_LINUX_VERBOSITY_1
2.180 + bool
2.181 + prompt "Full commands"
2.182 + help
2.183 + Print full command lines.
2.184 +
2.185 +config KERNEL_LINUX_VERBOSITY_2
2.186 + bool
2.187 + prompt "Exec reasons"
2.188 + help
2.189 + Print the reasons why a make target is rebuild.
2.190 +
2.191 +endchoice
2.192 +
2.193 +config KERNEL_LINUX_VERBOSE_LEVEL
2.194 + int
2.195 + default 0 if KERNEL_LINUX_VERBOSITY_0
2.196 + default 1 if KERNEL_LINUX_VERBOSITY_1
2.197 + default 2 if KERNEL_LINUX_VERBOSITY_2
2.198 +
2.199 +config KERNEL_LINUX_INSTALL_CHECK
2.200 + bool
2.201 + prompt "Check installed headers"
2.202 + default y
2.203 + help
2.204 + If you are in doubt that installed headers are buggy, say 'Y'
2.205 + here to have an extra check passed onto the headers.
2.206 +
2.207 +endif # KERNEL_LINUX_INSTALL
2.208 +
2.209 +if KERNEL_LINUX_USE_CUSTOM_HEADERS
2.210 +
2.211 +config KERNEL_LINUX_CUSTOM_IS_TARBALL
2.212 + bool
2.213 + prompt "This is a tarball"
2.214 + default n
2.215 + help
2.216 + If you say 'n' here, the path below is expected to point to a directory
2.217 + containing readily prepared headers
2.218 +
2.219 + If you say 'y' here, then the path below is expected to point to a
2.220 + tarball of such a directory.
2.221 +
2.222 + Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
2.223 + say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
2.224 +
2.225 + Now, passing a tarball around is easier than passing a directory, so
2.226 + if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
2.227 + say 'y' here, and enter the path to this tarball below.
2.228 +
2.229 +config KERNEL_LINUX_CUSTOM_PATH
2.230 + string
2.231 + prompt "Path to custom headers directory/tarball"
2.232 + help
2.233 + See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.
2.234 +
2.235 +endif # KERNEL_LINUX_USE_CUSTOM_HEADERS