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

     1 # Linux kernel options

     3 ## select KERNEL_SUPPORTS_SHARED_LIBS

     4 ##

     5 ## help Build a toolchain targeting systems running Linux as a kernel.

     7 config KERNEL_LINUX_USE_CUSTOM_HEADERS

     8     bool

     9     prompt "Use pre-installed headers tree (OBSOLETE)"

    10     depends on OBSOLETE

    11     help

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

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

    14       there, and into the toolchain's sysroot.

    16       Note:

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

    18       If you want to use your own full kernel tree, then you want to say 'N'

    19       here, and select KERNEL_LINUX_CUSTOM, in the versions list, below.

    21 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS

    23 choice

    24     bool

    25     prompt "Linux kernel version"

    26 # Don't remove next line

    27 # CT_INSERT_VERSION_BELOW

    29 config KERNEL_V_3_0_4

    30     bool

    31     prompt "3.0.4"

    33 config KERNEL_V_3_0_3

    34     bool

    35     prompt "3.0.3"

    37 config KERNEL_V_3_0_2

    38     bool

    39     prompt "3.0.2"

    41 config KERNEL_V_3_0_1

    42     bool

    43     prompt "3.0.1"

    45 config KERNEL_V_3_0

    46     bool

    47     prompt "3.0"

    49 config KERNEL_V_2_6_39_4

    50     bool

    51     prompt "2.6.39.4"

    53 config KERNEL_V_2_6_38_8

    54     bool

    55     prompt "2.6.38.8"

    57 config KERNEL_V_2_6_37_6

    58     bool

    59     prompt "2.6.37.6"

    61 config KERNEL_V_2_6_36_4

    62     bool

    63     prompt "2.6.36.4"

    65 config KERNEL_V_2_6_35_14

    66     bool

    67     prompt "2.6.35.14 (longterm)"

    68     help

    69       The Linux 2.6.35 tree is a "longterm" maintenance branch.

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

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

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

    75       which makes 2.6.35 a very useful base for many embedded developers seeking

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

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

    80       See the original announcement by Andi Kleen in the following mailing

    81       list entry:

    82         http://marc.info/?l=linux-kernel&m=129136895415202&w=4

    84 config KERNEL_V_2_6_34_10

    85     bool

    86     prompt "2.6.34.10"

    88 config KERNEL_V_2_6_33_19

    89     bool

    90     prompt "2.6.33.19"

    91     help

    92       This is primarily for the use of those people who are stuck using the

    93       .33-rt kernel.  Anyone else who really wants to use the .33 kernel tree

    94       is welcome to use this one as well.

    96 config KERNEL_V_2_6_32_46

    97     bool

    98     prompt "2.6.32.46 (longterm)"

    99     help

   100       The Linux 2.6.32 tree is a "longterm" maintenance branch.

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

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

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

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

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

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

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

   112       mailing list entry:

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

   115 config KERNEL_V_2_6_31_14

   116     bool

   117     prompt "2.6.31.14"

   119 config KERNEL_V_2_6_27_59

   120     bool

   121     prompt "2.6.27.59 (longterm)"

   122     help

   123       The Linux 2.6.27 tree is a "longterm" maintenance branch.

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

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

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

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

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

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

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

   135       entry:

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

   138       It is now maintained by Greg Kroah-Hartman, see this mailing list entry:

   139         http://marc.info/?l=linux-kernel&m=129133701916793&w=4

   141 config KERNEL_LINUX_CUSTOM

   142     bool

   143     prompt "custom tarball or directory"

   144     help

   145       Use a local tarball or local kernel directory of a complete kernel source tree.

   147 config KERNEL_LINUX_CUSTOM_LOCATION

   148     string

   149     prompt "Path to custom source, tarball or directory"

   150     depends on KERNEL_LINUX_CUSTOM

   151     help

   152       Enter here the path to the tarball of your full kernel tree or

   153       kernel directory

   155 endchoice

   157 config KERNEL_VERSION

   158     string

   159 # Don't remove next line

   160 # CT_INSERT_VERSION_STRING_BELOW

   161     default "3.0.4" if KERNEL_V_3_0_4

   162     default "3.0.3" if KERNEL_V_3_0_3

   163     default "3.0.2" if KERNEL_V_3_0_2

   164     default "3.0.1" if KERNEL_V_3_0_1

   165     default "3.0" if KERNEL_V_3_0

   166     default "2.6.39.4" if KERNEL_V_2_6_39_4

   167     default "2.6.38.8" if KERNEL_V_2_6_38_8

   168     default "2.6.37.6" if KERNEL_V_2_6_37_6

   169     default "2.6.36.4" if KERNEL_V_2_6_36_4

   170     default "2.6.35.14" if KERNEL_V_2_6_35_14

   171     default "2.6.34.10" if KERNEL_V_2_6_34_10

   172     default "2.6.33.19" if KERNEL_V_2_6_33_19

   173     default "2.6.32.46" if KERNEL_V_2_6_32_46

   174     default "2.6.31.14" if KERNEL_V_2_6_31_14

   175     default "2.6.27.59" if KERNEL_V_2_6_27_59

   176     default "custom" if KERNEL_LINUX_CUSTOM

   178 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS

   180 if KERNEL_LINUX_USE_CUSTOM_HEADERS

   182 config KERNEL_LINUX_CUSTOM_PATH

   183     string

   184     prompt "Path to custom headers directory/tarball"

   185     help

   186       See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.

   188 config KERNEL_LINUX_CUSTOM_IS_TARBALL

   189     bool

   190     prompt "This is a tarball"

   191     help

   192       If you say 'n' here, the path above is expected to point to a directory

   193       containing readily prepared headers

   195       If you say 'y' here, then the path above is expected to point to a

   196       tarball of such a directory.

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

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

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

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

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

   205 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS

author	Sinseman44 <sinseman44@gmail.com>
	Thu Sep 22 22:49:38 2011 +0200 (2011-09-22)
changeset 2680	b94e0f9d15a3
parent 2652	8e76355776c3
child 2734	c14996fd45ad
permissions	-rw-r--r--