config/kernel/linux.in
author "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
Thu Mar 15 13:05:31 2012 +0100 (2012-03-15)
changeset 2917 67fafa2647d1
parent 2907 9304d10c5d89
child 2921 856eacaf0e59
permissions -rw-r--r--
kernel/linux: update revisions

Update Linux with the latest available revisions.

Signed-off-by: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
     1 # Linux kernel options
     2 
     3 ## select KERNEL_SUPPORTS_SHARED_LIBS
     4 ##
     5 ## help Build a toolchain targeting systems running Linux as a kernel.
     6 
     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.
    15       
    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.
    20 
    21 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
    22 
    23 choice
    24     bool
    25     prompt "Linux kernel version"
    26 # Don't remove next line
    27 # CT_INSERT_VERSION_BELOW
    28 
    29 config KERNEL_V_3_2_11
    30     bool
    31     prompt "3.2.11"
    32 
    33 config KERNEL_V_3_2_10
    34     bool
    35     prompt "3.2.10"
    36 
    37 config KERNEL_V_3_2_9
    38     bool
    39     prompt "3.2.9"
    40 
    41 config KERNEL_V_3_2_8
    42     bool
    43     prompt "3.2.8"
    44 
    45 config KERNEL_V_3_2_7
    46     bool
    47     prompt "3.2.7"
    48 
    49 config KERNEL_V_3_2_6
    50     bool
    51     prompt "3.2.6"
    52 
    53 config KERNEL_V_3_2_5
    54     bool
    55     prompt "3.2.5"
    56 
    57 config KERNEL_V_3_2_4
    58     bool
    59     prompt "3.2.4"
    60 
    61 config KERNEL_V_3_2_3
    62     bool
    63     prompt "3.2.3"
    64 
    65 config KERNEL_V_3_2_2
    66     bool
    67     prompt "3.2.2"
    68 
    69 config KERNEL_V_3_2_1
    70     bool
    71     prompt "3.2.1"
    72 
    73 config KERNEL_V_3_2
    74     bool
    75     prompt "3.2"
    76 
    77 config KERNEL_V_3_1_10
    78     bool
    79     prompt "3.1.10"
    80 
    81 config KERNEL_V_3_0_24
    82     bool
    83     prompt "3.0.24"
    84 
    85 config KERNEL_V_2_6_39_4
    86     bool
    87     prompt "2.6.39.4"
    88 
    89 config KERNEL_V_2_6_38_8
    90     bool
    91     prompt "2.6.38.8"
    92 
    93 config KERNEL_V_2_6_37_6
    94     bool
    95     prompt "2.6.37.6"
    96 
    97 config KERNEL_V_2_6_36_4
    98     bool
    99     prompt "2.6.36.4"
   100 
   101 config KERNEL_V_2_6_33_20
   102     bool
   103     prompt "2.6.33.20"
   104     help
   105       This is primarily for the use of those people who are stuck using the
   106       .33-rt kernel.  Anyone else who really wants to use the .33 kernel tree
   107       is welcome to use this one as well.
   108 
   109 config KERNEL_V_2_6_32_58
   110     bool
   111     prompt "2.6.32.58 (longterm)"
   112     help
   113       The Linux 2.6.32 tree is a "longterm" maintenance branch.
   114       
   115       It is intended to fill the niche for users who are not using distribution
   116       kernels but want to use a regression-free kernel for a longer time.
   117       
   118       Critical bug fixes to later 2.6 releases are often ported to this branch
   119       which makes 2.6.32 a very useful base for many embedded developers seeking
   120       stable APIs or those who do not need the latest bleeding edge features.
   121       
   122       ... and no, this kernel has not undergone any specific QA testing.
   123       
   124       See the original announcement by Greg Kroah-Hartman in the following
   125       mailing list entry:
   126         http://marc.info/?l=linux-kernel&m=126384198403392&w=4
   127 
   128 config KERNEL_V_2_6_31_14
   129     bool
   130     prompt "2.6.31.14"
   131 
   132 config KERNEL_V_2_6_27_61
   133     bool
   134     prompt "2.6.27.61 (longterm)"
   135     help
   136       The Linux 2.6.27 tree is a "longterm" maintenance branch.
   137       
   138       It is intended to fill the niche for users who are not using distribution
   139       kernels but want to use a regression-free kernel for a longer time.
   140       
   141       Critical bug fixes to later 2.6 releases are often ported to this branch
   142       which makes 2.6.27 a very useful base for many embedded developers seeking
   143       stable APIs or those who do not need the latest bleeding edge features.
   144       
   145       ... and no, this kernel has not undergone any specific QA testing.
   146       
   147       See the original announcement by Adrian Bunk in the following mailing list
   148       entry:
   149         http://marc.info/?l=linux-kernel&m=122375909403298&w=4
   150       
   151       It is now maintained by Greg Kroah-Hartman, see this mailing list entry:
   152         http://marc.info/?l=linux-kernel&m=129133701916793&w=4
   153 
   154 config KERNEL_LINUX_CUSTOM
   155     bool
   156     prompt "custom tarball or directory"
   157     help
   158       Use a local tarball or local kernel directory of a complete kernel source tree.
   159 
   160 config KERNEL_LINUX_CUSTOM_LOCATION
   161     string
   162     prompt "Path to custom source, tarball or directory"
   163     depends on KERNEL_LINUX_CUSTOM
   164     help
   165       Enter here the path to the tarball of your full kernel tree or
   166       kernel directory
   167 
   168 endchoice
   169 
   170 config KERNEL_VERSION
   171     string
   172 # Don't remove next line
   173 # CT_INSERT_VERSION_STRING_BELOW
   174     default "3.2.11" if KERNEL_V_3_2_11
   175     default "3.2.10" if KERNEL_V_3_2_10
   176     default "3.2.9" if KERNEL_V_3_2_9
   177     default "3.2.8" if KERNEL_V_3_2_8
   178     default "3.2.7" if KERNEL_V_3_2_7
   179     default "3.2.6" if KERNEL_V_3_2_6
   180     default "3.2.5" if KERNEL_V_3_2_5
   181     default "3.2.4" if KERNEL_V_3_2_4
   182     default "3.2.3" if KERNEL_V_3_2_3
   183     default "3.2.2" if KERNEL_V_3_2_2
   184     default "3.2.1" if KERNEL_V_3_2_1
   185     default "3.2" if KERNEL_V_3_2
   186     default "3.1.10" if KERNEL_V_3_1_10
   187     default "3.0.24" if KERNEL_V_3_0_24
   188     default "2.6.39.4" if KERNEL_V_2_6_39_4
   189     default "2.6.38.8" if KERNEL_V_2_6_38_8
   190     default "2.6.37.6" if KERNEL_V_2_6_37_6
   191     default "2.6.36.4" if KERNEL_V_2_6_36_4
   192     default "2.6.33.20" if KERNEL_V_2_6_33_20
   193     default "2.6.32.58" if KERNEL_V_2_6_32_58
   194     default "2.6.31.14" if KERNEL_V_2_6_31_14
   195     default "2.6.27.61" if KERNEL_V_2_6_27_61
   196     default "custom" if KERNEL_LINUX_CUSTOM
   197 
   198 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS
   199 
   200 if KERNEL_LINUX_USE_CUSTOM_HEADERS
   201 
   202 config KERNEL_LINUX_CUSTOM_PATH
   203     string
   204     prompt "Path to custom headers directory/tarball"
   205     help
   206       See KERNEL_LINUX_CUSTOM_IS_TARBALL, below.
   207 
   208 config KERNEL_LINUX_CUSTOM_IS_TARBALL
   209     bool
   210     prompt "This is a tarball"
   211     help
   212       If you say 'n' here, the path above is expected to point to a directory
   213       containing readily prepared headers
   214       
   215       If you say 'y' here, then the path above is expected to point to a
   216       tarball of such a directory.
   217       
   218       Eg., if your headers are available in: /foo/bar/buz/my_hdrs/include,
   219       say 'n' here, and enter: /foo/bar/buz/my_hdrs below.
   220       
   221       Now, passing a tarball around is easier than passing a directory, so
   222       if you want to, you can make a tarball of /foo/bar/buz/my_hdrs/include,
   223       say 'y' here, and enter the path to this tarball below.
   224 
   225 endif # KERNEL_LINUX_USE_CUSTOM_HEADERS