crosstool-ng: config/kernel/linux.in@cff04df67d28

     1 # Linux kernel options

     3 # Linux kernel options

     5 config KERNEL_linux

     6     select KERNEL_SUPPORTS_SHARED_LIBS

     7     help

     8       Build a toolchain targeting systems running Linux as a kernel.

    10 choice

    11     bool

    12     prompt "Get kernel headers from:"

    14 config KERNEL_LINUX_INSTALL

    15     bool

    16     prompt "kernel's 'headers_install'"

    17     help

    18       This will make use of the new headers_install rule in recent kernels.

    19       This is most probably what you want to use.

    21 if KERNEL_LINUX_INSTALL

    23 choice

    24     bool

    25     prompt "Linux kernel version"

    26 # Don't remove next line

    27 # CT_INSERT_VERSION_BELOW

    29 config KERNEL_V_2_6_36

    30     bool

    31     prompt "2.6.36"

    33 config KERNEL_V_2_6_35_7

    34     bool

    35     prompt "2.6.35.7"

    37 config KERNEL_V_2_6_35_6

    38     bool

    39     prompt "2.6.35.6"

    41 config KERNEL_V_2_6_35_5

    42     bool

    43     prompt "2.6.35.5"

    45 config KERNEL_V_2_6_35_4

    46     bool

    47     prompt "2.6.35.4"

    49 config KERNEL_V_2_6_35_3

    50     bool

    51     prompt "2.6.35.3"

    53 config KERNEL_V_2_6_35_2

    54     bool

    55     prompt "2.6.35.2"

    57 config KERNEL_V_2_6_35_1

    58     bool

    59     prompt "2.6.35.1"

    61 config KERNEL_V_2_6_35

    62     bool

    63     prompt "2.6.35"

    65 config KERNEL_V_2_6_34_7

    66     bool

    67     prompt "2.6.34.7"

    69 config KERNEL_V_2_6_33_7

    70     bool

    71     prompt "2.6.33.7"

    73 config KERNEL_V_2_6_32_24

    74     bool

    75     prompt "2.6.32.24 (long-term stable)"

    76     help

    77       The Linux 2.6.32 tree is the current "long-term stable" maintenance branch.

    78       It is intended to fill the niche for users who are not using distribution

    79       kernels but want to use a regression-free kernel for a longer time.

    81       Critical bug fixes to later 2.6 releases are often ported to this branch

    82       which makes 2.6.32 a very useful base for many embedded developers seeking

    83       stable APIs or those who do not need the latest bleeding edge features.

    85       ... and no, this kernel has not undergone any specific QA testing.

    87       See the original announcement by Greg Kroah-Hartman in the following

    88       mailing list entry:

    89         http://marc.info/?l=linux-kernel&m=126384198403392&w=2

    91 config KERNEL_V_2_6_31_14

    92     bool

    93     prompt "2.6.31.14"

    95 config KERNEL_V_2_6_27_54

    96     bool

    97     prompt "2.6.27.54 (old long-term stable)"

    98     help

    99       The Linux 2.6.27 tree is the previous "long-term stable" maintenance branch.

   100       It is intended to fill the niche for users who are not using distribution

   101       kernels but want to use a regression-free kernel for a longer time.

   103       Critical bug fixes to later 2.6 releases are often ported to this branch

   104       which makes 2.6.27 a very useful base for many embedded developers seeking

   105       stable APIs or those who do not need the latest bleeding edge features.

   107       ... and no, this kernel has not undergone any specific QA testing.

   109       See the original announcement by Adrian Bunk in the following mailing list

   110       entry:

   111         http://marc.info/?l=linux-kernel&m=122375909403298&w=2

   113 config KERNEL_LINUX_CUSTOM

   114     bool

   115     prompt "custom tarball"

   116     help

   117       Use a local tarball of a complete kernel source tree.

   119 config KERNEL_LINUX_CUSTOM_TARBALL

   120     string

   121     prompt "Path to custom tarball"

   122     depends on KERNEL_LINUX_CUSTOM

   123     help

   124       Enter here the path to the tarball of your full kernel tree.

   126 endchoice

   128 config KERNEL_VERSION

   129     string

   130 # Don't remove next line

   131 # CT_INSERT_VERSION_STRING_BELOW

   132     default "2.6.36" if KERNEL_V_2_6_36

   133     default "2.6.35.7" if KERNEL_V_2_6_35_7

   134     default "2.6.35.6" if KERNEL_V_2_6_35_6

   135     default "2.6.35.5" if KERNEL_V_2_6_35_5

   136     default "2.6.35.4" if KERNEL_V_2_6_35_4

   137     default "2.6.35.3" if KERNEL_V_2_6_35_3

   138     default "2.6.35.2" if KERNEL_V_2_6_35_2

   139     default "2.6.35.1" if KERNEL_V_2_6_35_1

   140     default "2.6.35" if KERNEL_V_2_6_35

   141     default "2.6.34.7" if KERNEL_V_2_6_34_7

   142     default "2.6.33.7" if KERNEL_V_2_6_33_7

   143     default "2.6.32.24" if KERNEL_V_2_6_32_24

   144     default "2.6.31.14" if KERNEL_V_2_6_31_14

   145     default "2.6.27.54" if KERNEL_V_2_6_27_54

   147 choice

   148     bool

   149     prompt "Kernel verbosity:"

   150     default KERNEL_LINUX_VERBOSITY_0

   152 config KERNEL_LINUX_VERBOSITY_0

   153     bool

   154     prompt "Simplified"

   155     help

   156       Print simplified command lines.

   158 config KERNEL_LINUX_VERBOSITY_1

   159     bool

   160     prompt "Full commands"

   161     help

   162       Print full command lines.

   164 config KERNEL_LINUX_VERBOSITY_2

   165     bool

   166     prompt "Exec reasons"

   167     help

   168       Print the reasons why a make target is rebuild.

   170 endchoice

   172 config KERNEL_LINUX_VERBOSE_LEVEL

   173     int

   174     default 0 if KERNEL_LINUX_VERBOSITY_0

   175     default 1 if KERNEL_LINUX_VERBOSITY_1

   176     default 2 if KERNEL_LINUX_VERBOSITY_2

   178 config KERNEL_LINUX_INSTALL_CHECK

   179     bool

   180     prompt "Check installed headers"

   181     default y

   182     help

   183       If you are in doubt that installed headers are buggy, say 'Y'

   184       here to have an extra check passed onto the headers.

   186 endif # KERNEL_LINUX_INSTALL

   188 config KERNEL_LINUX_USE_CUSTOM_HEADERS

   189     bool

   190     prompt "pre-installed headers tree"

   191     help

   192       If you have some pre-installed kernel headers lying around, you can

   193       enter the path to these headers, below, they will be copied from

   194       there, and into the toolchain's sysroot.

   196       Note:

   197       This will *not* let you use a complete kernel tree!

   198       If you want to use your own full kernel tree, then you want to

   199       say 'Y' to KERNEL_LINUX_INSTALL, above, and select KERNEL_LINUX_CUSTOM.

   201 if KERNEL_LINUX_USE_CUSTOM_HEADERS

   203 config KERNEL_LINUX_CUSTOM_IS_TARBALL

   204     bool

   205     prompt "This is a tarball"

   206     default n

   207     help

   208       If you say 'n' here, the path below is expected to point to a directory

   209       containing readily prepared headers

   211       If you say 'y' here, then the path below is expected to point to a

   212       tarball of such a directory.

   214       Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,

   215       say 'n' here, and enter: /foo/bar/buz/my_hdrs below.

   217       Now, passing a tarball around is easier than passing a directory, so

   218       if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,

   219       say 'y' here, and enter the path to this tarball below.

   221 config KERNEL_LINUX_CUSTOM_PATH

   222     string

   223     prompt "Path to custom headers directory/tarball"

   224     help

   225       See KERNEL_LINUX_CUSTOM_IS_TARBALL, above.

   227 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS

   229 endchoice

author	"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
	Sat Oct 23 23:28:48 2010 +0200 (2010-10-23)
changeset 2158	cff04df67d28
parent 2136	750cf0d26370
child 2159	c27380b72046
permissions	-rw-r--r--