summaryrefslogtreecommitdiff
path: root/config/kernel/kernel_linux.in
diff options
context:
space:
mode:
Diffstat (limited to 'config/kernel/kernel_linux.in')
-rw-r--r--config/kernel/kernel_linux.in134
1 files changed, 134 insertions, 0 deletions
diff --git a/config/kernel/kernel_linux.in b/config/kernel/kernel_linux.in
new file mode 100644
index 0000000..cb5348e
--- /dev/null
+++ b/config/kernel/kernel_linux.in
@@ -0,0 +1,134 @@
+# Linux kernel options
+
+choice
+ bool
+ prompt "Get kernel headers from:"
+
+config KERNEL_LINUX_HEADERS_INSTALL
+ bool
+ prompt "kernel's 'headers_install'"
+ help
+ This will make use of the new headers_install rule in recent kernels.
+ This is most probably what you want to use.
+
+config KERNEL_LINUX_HEADERS_SANITISED
+ bool
+ prompt "Mazur's sanitized headers (OBSOLETE)"
+ depends on OBSOLETE
+ select KERNEL_LINUX_NEEDS_CONFIG
+ help
+ M. Mazur used to maintain a tree of sanitised headers, but it is now
+ obsoleted by the headers_install rule (above), and has not seen any
+ update since 2.6.12
+
+config KERNEL_LINUX_HEADERS_COPY
+ bool
+ prompt "pure kernel headers (REALLY OBSOLETE)"
+ depends on OBSOLETE
+ select KERNEL_LINUX_NEEDS_CONFIG
+ help
+ This will simply copy the kernel headers to the toolchain.
+
+ You do NOT want this. It's badly broken because it leaks kernel internals
+ to userspace.
+
+config KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
+ bool
+ prompt "Use custom directory"
+ help
+ If you have some kernel headers lying around, you can enter the path
+ below.
+
+endchoice
+
+config KERNEL
+ string
+ default "linux" if ! KERNEL_LINUX_HEADERS_SANITISED
+ default "linux-libc-headers" if KERNEL_LINUX_HEADERS_SANITISED
+
+config KERNEL_VERSION_SEE_EXTRAVERSION
+ bool
+ prompt "See extra versions"
+ default n
+ depends on KERNEL_LINUX_HEADERS_COPY || KERNEL_LINUX_HEADERS_INSTALL
+ help
+ See extra versions (kernel with 4 numbers, eg 2.6.19.1).
+
+ If you say 'no', you'll only see sub-level, 3-digit versions.
+ If you say 'yes', you'll see far more versions!
+
+ It is recommended that you say 'no', unless you _*know*_
+ that an extra version fixes a headers bug.
+
+if KERNEL_LINUX_HEADERS_INSTALL
+source config/kernel/kernel_linux_headers_install.in
+endif
+
+if KERNEL_LINUX_HEADERS_COPY
+source config/kernel/kernel_linux_headers_copy.in
+endif
+
+if KERNEL_LINUX_HEADERS_SANITISED
+source config/kernel/kernel_linux_headers_sanitised.in
+endif
+
+config KERNEL_LINUX_HEADERS_CUSTOM_DIR
+ string
+ prompt "Where are those custom headers?"
+ depends on KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
+ help
+ Enter the base directory where the headers are to be found.
+
+ Eg. if the headers are in /some/place/include, then enter /some/place.
+ This is the same path you entered when you typed:
+ make INSTALL_HDR_PATH=/some/place headers_install
+
+if ! KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR
+
+choice
+ bool
+ prompt "Kernel verbosity:"
+ default KERNEL_LINUX_VERBOSITY_0
+
+config KERNEL_LINUX_VERBOSITY_0
+ bool
+ prompt "Simplified"
+ help
+ Print simplified command lines.
+
+config KERNEL_LINUX_VERBOSITY_1
+ bool
+ prompt "Full commands"
+ help
+ Print full command lines.
+
+config KERNEL_LINUX_VERBOSITY_2
+ bool
+ prompt "Exec reasons"
+ help
+ Print the reasons why a make target is rebuild.
+
+endchoice
+
+config KERNEL_LINUX_VERBOSE_LEVEL
+ int
+ default 0 if KERNEL_LINUX_VERBOSITY_0
+ default 1 if KERNEL_LINUX_VERBOSITY_1
+ default 2 if KERNEL_LINUX_VERBOSITY_2
+
+config KERNEL_LINUX_NEEDS_CONFIG
+ bool
+ default n
+
+config KERNEL_LINUX_CONFIG_FILE
+ string
+ prompt "Configuration file"
+ depends on KERNEL_LINUX_NEEDS_CONFIG
+ default ""
+ help
+ Path to a kernel configuration file.
+
+ If you don't provide one, then the default configuration for
+ your target will be used.
+
+endif