cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/pkgs/os-specific/linux/kernel/common-config.nix

451 lines
12 KiB
Nix
Raw Normal View History

kernel: add a warning/note at the top of common-config so that people would hopefully stop breaking the older kernels
2015-03-24 22:34:54 +01:00
/*
WARNING/NOTE: whenever you want to add an option here you need to
either
* mark it as an optional one with `?` suffix,
* or make sure it works for all the versions in nixpkgs,
* or check for which kernel versions it will work (using kernel
changelog, google or whatever) and mark it with `versionOlder` or
`versionAtLeast`.
Then do test your change by building all the kernels (or at least
their configs) in nixpkgs or else you will guarantee lots and lots
of pain to users trying to switch to an older kernel because of some
hardware problems with a new one.
*/
kernel: allow features to be used in common-config Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-08 00:26:33 +02:00
{ stdenv, version, kernelPlatform, extraConfig, features }:
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
with stdenv.lib;
''
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
# Debugging.
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
DEBUG_KERNEL y
TIMER_STATS y
BACKTRACE_SELF_TEST n
CPU_NOTIFIER_ERROR_INJECT? n
DEBUG_DEVRES n
DEBUG_NX_TEST n
DEBUG_STACK_USAGE n
linux: Disable CONFIG_DEBUG_STACKOVERFLOW This got enabled accidentally in e64e3ad88ab612379747dff15b62573bda3f8de4.
2015-03-02 23:34:44 +01:00
${optionalString (!(features.grsecurity or false)) ''
kernel: only use DEBUG_STACKOVERFLOW if !grsecurity Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 15:56:52 +02:00
DEBUG_STACKOVERFLOW n
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
RCU_TORTURE_TEST n
SCHEDSTATS n
linux: Enable detection of hung tasks
2013-08-01 00:50:48 +02:00
DETECT_HUNG_TASK y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
# Power management.
${optionalString (versionOlder version "3.19") ''
PM_RUNTIME y
''}
PM_ADVANCED_DEBUG y
${optionalString (versionAtLeast version "3.10") ''
X86_INTEL_PSTATE y
''}
linux: Enable Intel idle driver Also build the performance governor into the kernel so there is a sane default. Note that cpufreq.service will still load "ondemand" on non-pstate systems.
2015-03-04 17:04:02 +01:00
INTEL_IDLE y
CPU_FREQ_DEFAULT_GOV_PERFORMANCE y
Kernel config: Separate power management and debugging
2015-03-04 16:37:42 +01:00
${optionalString (versionOlder version "3.10") ''
USB_SUSPEND y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Support drivers that need external firmware.
STANDALONE n
Revert "linux: really provide /proc/config.gz" This reverts commit 68ce9e91e12914f34e55ef16d8f4b6fbcdd9e92a. /proc/config.gz is available after "modprobe configs" and in /run/booted-system/kernel-modules/config
2013-09-04 06:45:36 +02:00
# Make /proc/config.gz available.
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
IKCONFIG_PROC y
# Optimize with -O2, not -Os.
CC_OPTIMIZE_FOR_SIZE n
# Enable the kernel's built-in memory tester.
MEMTEST y
# Include the CFQ I/O scheduler in the kernel, rather than as a
# module, so that the initrd gets a good I/O scheduler.
IOSCHED_CFQ y
BLK_CGROUP y # required by CFQ
# Enable NUMA.
NUMA? y
# Disable some expensive (?) features.
PM_TRACE_RTC n
# Enable various subsystems.
ACCESSIBILITY y # Accessibility support
AUXDISPLAY y # Auxiliary Display support
DONGLE y # Serial dongle support
HIPPI y
MTD_COMPLEX_MAPPINGS y # needed for many devices
${optionalString (versionOlder version "3.2") ''
NET_POCKET y # enable pocket and portable adapters
''}
SCSI_LOWLEVEL y # enable lots of SCSI devices
SCSI_LOWLEVEL_PCMCIA y
Added line SCSI_SAS_ATA y on line 62 This kernel change will make the nixOS live cd detect the hard drive upon boot.
2014-10-17 22:31:08 +02:00
SCSI_SAS_ATA y # added to enable detection of hard drive
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
SPI y # needed for many devices
SPI_MASTER y
WAN y
# Networking options.
IP_PNP n
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
${optionalString (versionOlder version "3.13") ''
linux: Enable BPF_JIT only on 64-bit It's not supported on i686. http://hydra.nixos.org/build/16834647
2014-11-10 20:21:28 +01:00
IPV6_PRIVACY y
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
NETFILTER_ADVANCED y
IP_VS_PROTO_TCP y
IP_VS_PROTO_UDP y
IP_VS_PROTO_ESP y
IP_VS_PROTO_AH y
IP_DCCP_CCID3 n # experimental
CLS_U32_PERF y
CLS_U32_MARK y
linux: Enable BPF_JIT only on 64-bit It's not supported on i686. http://hydra.nixos.org/build/16834647
2014-11-10 20:21:28 +01:00
${optionalString (stdenv.system == "x86_64-linux") ''
BPF_JIT y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Wireless networking.
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
CFG80211_WEXT? y # Without it, ipw2200 drivers don't build
IPW2100_MONITOR? y # support promiscuous mode
IPW2200_MONITOR? y # support promiscuous mode
HOSTAP_FIRMWARE? y # Support downloading firmware images with Host AP driver
HOSTAP_FIRMWARE_NVRAM? y
ATH9K_PCI? y # Detect Atheros AR9xxx cards on PCI(e) bus
ATH9K_AHB? y # Ditto, AHB bus
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${optionalString (versionAtLeast version "3.2") ''
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
B43_PHY_HT? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
''}
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
BCMA_HOST_PCI? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Enable various FB devices.
FB y
FB_EFI y
FB_NVIDIA_I2C y # Enable DDC Support
FB_RIVA_I2C y
FB_ATY_CT y # Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
FB_ATY_GX y # Mach64 GX support
FB_SAVAGE_I2C y
FB_SAVAGE_ACCEL y
FB_SIS_300 y
FB_SIS_315 y
FB_3DFX_ACCEL y
linux 3.11 works fine for me, but nvidia binary driver fails once again
2013-09-04 06:49:22 +02:00
${optionalString (versionOlder version "3.9" || stdenv.system == "i686-linux") ''
FB_GEODE y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Video configuration.
# Enable KMS for devices whose X.org driver supports it.
DRM_I915_KMS y
${optionalString (versionOlder version "3.9") ''
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
DRM_RADEON_KMS? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
''}
# Hybrid graphics support
VGA_SWITCHEROO y
# Sound.
linux: Enable SND_DYNAMIC_MINORS This is necessary if you get: kernel: Too many HDMI devices kernel: Consider building the kernel with CONFIG_SND_DYNAMIC_MINORS=y
2014-04-18 21:06:34 +02:00
SND_DYNAMIC_MINORS y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
SND_AC97_POWER_SAVE y # AC97 Power-Saving Mode
SND_HDA_INPUT_BEEP y # Support digital beep via input layer
SND_USB_CAIAQ_INPUT y
PSS_MIXER y # Enable PSS mixer (Beethoven ADSP-16 and other compatible)
# USB serial devices.
USB_SERIAL_GENERIC y # USB Generic Serial Driver
USB_SERIAL_KEYSPAN_MPR y # include firmware for various USB serial devices
USB_SERIAL_KEYSPAN_USA28 y
USB_SERIAL_KEYSPAN_USA28X y
USB_SERIAL_KEYSPAN_USA28XA y
USB_SERIAL_KEYSPAN_USA28XB y
USB_SERIAL_KEYSPAN_USA19 y
USB_SERIAL_KEYSPAN_USA18X y
USB_SERIAL_KEYSPAN_USA19W y
USB_SERIAL_KEYSPAN_USA19QW y
USB_SERIAL_KEYSPAN_USA19QI y
USB_SERIAL_KEYSPAN_USA49W y
USB_SERIAL_KEYSPAN_USA49WLC y
# Filesystem options - in particular, enable extended attributes and
# ACLs for all filesystems that support them.
kernel: common-config.nix: enable FANOTIFY
2015-02-12 19:39:44 +01:00
FANOTIFY y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
EXT2_FS_XATTR y
EXT2_FS_POSIX_ACL y
linux: Enable ACLs in ext3 http://hydra.nixos.org/build/13462892
2014-08-18 14:33:09 +02:00
EXT2_FS_SECURITY y
linux/kernel: Remove EXT2_FS_XIP for version 4.0. The option has been removed in torvalds/linux@6cd176a and thus we shouldn't try to set it for kernel version 4. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-03-04 15:38:17 +01:00
${optionalString (versionOlder version "4.0") ''
EXT2_FS_XIP y # Ext2 execute in place support
''}
linux: Enable ACLs in ext3 http://hydra.nixos.org/build/13462892
2014-08-18 14:33:09 +02:00
EXT3_FS_POSIX_ACL y
EXT3_FS_SECURITY y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
EXT4_FS_POSIX_ACL y
EXT4_FS_SECURITY y
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
REISERFS_FS_XATTR? y
REISERFS_FS_POSIX_ACL? y
REISERFS_FS_SECURITY? y
JFS_POSIX_ACL? y
JFS_SECURITY? y
XFS_QUOTA? y
XFS_POSIX_ACL? y
XFS_RT? y # XFS Realtime subvolume support
OCFS2_DEBUG_MASKLOG? n
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
BTRFS_FS_POSIX_ACL y
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
UBIFS_FS_ADVANCED_COMPR? y
linux: only enable CONFIG_NFS_SWAP for v3.6+ kernels Linux v3.6 is the earliest version with CONFIG_NFS_SWAP support. This change unbreaks NixOS tests for older kernels.
2014-07-16 12:08:48 +02:00
${optionalString (versionAtLeast version "3.6") ''
NFS_SWAP y
''}
linux: Enable NFSv4.1, v4.2 clients and swap on NFS I'm only enabling for kernels >= 3.11 to be conservative, because clients and servers automatically negotiate and use the highest mutually supported version by default, but only in kernel 3.11 server NFSv4.1 support actually became RFC compliant. I'm also adding support for swap on NFS, which is enabled by default on Ubuntu kernels.
2014-04-23 16:47:50 +02:00
${optionalString (versionAtLeast version "3.11") ''
NFS_V4_1 y # NFSv4.1 client support
NFS_V4_2 y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
NFSD_V2_ACL y
NFSD_V3 y
NFSD_V3_ACL y
NFSD_V4 y
NFS_FSCACHE y
CIFS_XATTR y
CIFS_POSIX y
CIFS_FSCACHE y
kernel: Add more supported features
2014-11-08 11:44:19 +01:00
${optionalString (versionAtLeast version "3.12") ''
CEPH_FSCACHE y
''}
${optionalString (versionAtLeast version "3.14") ''
CEPH_FS_POSIX_ACL y
''}
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.13") ''
SQUASHFS_FILE_DIRECT y
SQUASHFS_DECOMP_MULTI_PERCPU y
''}
Change kernel config: improve squashfs support of kernel
2015-02-16 19:42:10 +01:00
SQUASHFS_XATTR y
SQUASHFS_ZLIB y
SQUASHFS_LZO y
SQUASHFS_XZ y
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.19") ''
SQUASHFS_LZ4 y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Security related features.
STRICT_DEVMEM y # Filter access to /dev/mem
linux: Disable /dev/kmem See e.g. https://wiki.ubuntu.com/Security/Features#A.2BAC8-dev.2BAC8-kmem_disabled
2013-08-01 00:08:44 +02:00
SECURITY_SELINUX_BOOTPARAM_VALUE 0 # Disable SELinux by default
grsec: refactor grsecurity packages This now provides a handful of different grsecurity kernels for slightly different 'flavors' of packages. This doesn't change the grsecurity module to use them just yet, however. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-14 19:04:40 +02:00
DEVKMEM? n # Disable /dev/kmem
Enable CC_STACKPROTECTOR_REGULAR on linux 3.14+
2014-04-02 23:58:54 +02:00
${if versionOlder version "3.14" then ''
kernel/common-config: Another optional option Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 02:44:03 +02:00
CC_STACKPROTECTOR? y # Detect buffer overflows on the stack
Enable CC_STACKPROTECTOR_REGULAR on linux 3.14+
2014-04-02 23:58:54 +02:00
'' else ''
kernel/common-config: Another optional option Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 02:44:03 +02:00
CC_STACKPROTECTOR_REGULAR? y
Add linux 3.14
2014-04-01 02:54:47 +02:00
''}
kernel: add linux 3.12-rc2
2013-09-25 12:49:49 +02:00
${optionalString (versionAtLeast version "3.12") ''
USER_NS y # Support for user namespaces
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
kernel: enable AppArmor by default AppArmor only requires a few patches to the 3.2 and 3.4 kernels in order to work properly (with the minor catch grsecurity -stable includes the 3.2 patches.) This adds them to the kernel builds by default, removes features.apparmor (since it's always true) and makes it the default MAC system. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-08 00:59:29 +02:00
# AppArmor support
SECURITY_APPARMOR y
DEFAULT_SECURITY_APPARMOR y
kernel-config: Add microcode support + early loading on new kernels
2015-03-25 19:29:57 +01:00
# Microcode loading support
MICROCODE y
MICROCODE_INTEL y
MICROCODE_AMD y
${optionalString (versionAtLeast version "3.11") ''
MICROCODE_EARLY y
MICROCODE_INTEL_EARLY y
MICROCODE_AMD_EARLY y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Misc. options.
8139TOO_8129 y
8139TOO_PIO n # PIO is slower
AIC79XX_DEBUG_ENABLE n
AIC7XXX_DEBUG_ENABLE n
AIC94XX_DEBUG n
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
${optionalString (versionAtLeast version "3.3" && versionOlder version "3.13") ''
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
AUDIT_LOGINUID_IMMUTABLE y
''}
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
B43_PCMCIA? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
BLK_DEV_CMD640_ENHANCED y # CMD640 enhanced support
BLK_DEV_IDEACPI y # IDE ACPI support
BLK_DEV_INTEGRITY y
BSD_PROCESS_ACCT_V3 y
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
BT_HCIUART_BCSP? y
BT_HCIUART_H4? y # UART (H4) protocol support
BT_HCIUART_LL? y
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.4") ''
BT_RFCOMM_TTY? y # RFCOMM TTY support
''}
Turning off PAE support which makes kernel unbootable on older hardware causes CRASH_DUMP option to disappear, so make it optional.
2013-08-12 04:30:10 +02:00
CRASH_DUMP? n
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${optionalString (versionOlder version "3.1") ''
DMAR? n # experimental
''}
DVB_DYNAMIC_MINORS? y # we use udev
${optionalString (versionAtLeast version "3.3") ''
EFI_STUB y # EFI bootloader in the bzImage itself
''}
FHANDLE y # used by systemd
FUSION y # Fusion MPT device support
IDE_GD_ATAPI y # ATAPI floppy support
IRDA_ULTRA y # Ultra (connectionless) protocol
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
JOYSTICK_IFORCE_232? y # I-Force Serial joysticks and wheels
JOYSTICK_IFORCE_USB? y # I-Force USB joysticks and wheels
JOYSTICK_XPAD_FF? y # X-Box gamepad rumble support
JOYSTICK_XPAD_LEDS? y # LED Support for Xbox360 controller 'BigX' LED
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
LDM_PARTITION y # Windows Logical Disk Manager (Dynamic Disk) support
LEDS_TRIGGER_IDE_DISK y # LED IDE Disk Trigger
LOGIRUMBLEPAD2_FF y # Logitech Rumblepad 2 force feedback
LOGO n # not needed
MEDIA_ATTACH y
MEGARAID_NEWGEN y
MODVERSIONS y
MOUSE_PS2_ELANTECH y # Elantech PS/2 protocol extension
MTRR_SANITIZER y
NET_FC y # Fibre Channel driver support
PPP_MULTILINK y # PPP multilink support
kernel: Enable PPP_FILTER by default. pppd will try to use it to improve efficiency and complain if it's not available (but is is not mandatory).
2014-11-02 13:39:14 +01:00
PPP_FILTER y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
REGULATOR y # Voltage and Current Regulator Support
${optionalString (versionAtLeast version "3.6") ''
RC_DEVICES? y # Enable IR devices
''}
fix linux 3.2/3.4 builds
2015-03-29 21:40:57 +02:00
${optionalString (versionAtLeast version "3.10") ''
RT2800USB_RT55XX y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
SCSI_LOGGING y # SCSI logging facility
SERIAL_8250 y # 8250/16550 and compatible serial support
SLIP_COMPRESSED y # CSLIP compressed headers
SLIP_SMART y
THERMAL_HWMON y # Hardware monitoring support
linux: disable UEVENT_HELPER by default on versions >= 3.15
2015-04-06 14:00:03 +02:00
${optionalString (versionAtLeast version "3.15") ''
UEVENT_HELPER n
''}
kernel/common-config: More fixes
2015-03-20 23:05:43 +01:00
${optionalString (versionOlder version "3.15") ''
USB_DEBUG? n
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
USB_EHCI_ROOT_HUB_TT y # Root Hub Transaction Translators
USB_EHCI_TT_NEWSCHED y # Improved transaction translator scheduling
X86_CHECK_BIOS_CORRUPTION y
X86_MCE y
# Linux containers.
RT_GROUP_SCHED? y
CGROUP_DEVICE? y
${if versionAtLeast version "3.6" then ''
MEMCG y
MEMCG_SWAP y
'' else ''
CGROUP_MEM_RES_CTLR y
CGROUP_MEM_RES_CTLR_SWAP y
''}
DEVPTS_MULTIPLE_INSTANCES y
linux: Enable proper blkio controller support Having BLK_CGROUP is not enough, you need BLK_DEV_THROTTLING or CFQ_GROUP_IOSCHED to do anything useful.
2013-09-17 16:00:36 +02:00
BLK_DEV_THROTTLING y
CFQ_GROUP_IOSCHED y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Enable staging drivers. These are somewhat experimental, but
# they generally don't hurt.
STAGING y
# PROC_EVENTS requires that the netlink connector is not built
# as a module. This is required by libcgroup's cgrulesengd.
CONNECTOR y
PROC_EVENTS y
# Tracing.
FTRACE y
kernel: Enable kprobes and other tracing features All of these should have minimal performance impact unless enabled at runtime.
2015-03-11 17:11:41 +01:00
KPROBES y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
FUNCTION_TRACER y
FTRACE_SYSCALLS y
SCHED_TRACER y
kernel: Enable kprobes and other tracing features All of these should have minimal performance impact unless enabled at runtime.
2015-03-11 17:11:41 +01:00
STACK_TRACER y
kernel/common-config: Fix older kernels
2015-03-20 22:41:03 +01:00
${optionalString (versionAtLeast version "3.10") ''
UPROBE_EVENT y
''}
kernel: Enable kprobes and other tracing features All of these should have minimal performance impact unless enabled at runtime.
2015-03-11 17:11:41 +01:00
FUNCTION_PROFILER y
RING_BUFFER_BENCHMARK n
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Devtmpfs support.
DEVTMPFS y
# Easier debugging of NFS issues.
${optionalString (versionAtLeast version "3.4") ''
SUNRPC_DEBUG y
''}
# Virtualisation.
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
PARAVIRT? y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
${if versionAtLeast version "3.10" then ''
kernel/grsec: another optional option This should fix the testing kernels. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 15:57:08 +02:00
HYPERVISOR_GUEST? y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
'' else ''
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
PARAVIRT_GUEST? y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
''}
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
KVM_GUEST? y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
${optionalString (versionOlder version "3.7") ''
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
KVM_CLOCK? y
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
''}
kernel: make some common-config options optional for grsec Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-17 23:28:56 +02:00
XEN? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
XEN_DOM0? y
Add kernel config for dom0 of Xen
2015-02-10 16:53:03 +01:00
${optionalString ((versionAtLeast version "3.18") && (features.xen_dom0 or false)) ''
PCI_XEN? y
HVC_XEN? y
HVC_XEN_FRONTEND? y
XEN_SYS_HYPERVISOR? y
SWIOTLB_XEN? y
XEN_BACKEND? y
XEN_BALLOON? y
XEN_BALLOON_MEMORY_HOTPLUG? y
XEN_EFI? y
XEN_HAVE_PVMMU? y
XEN_MCE_LOG? y
XEN_PVH? y
XEN_PVHVM? y
XEN_SAVE_RESTORE? y
XEN_SCRUB_PAGES? y
XEN_SELFBALLOONING? y
XEN_STUB? y
XEN_TMEM? y
''}
Move kernelExtraConfig to common-config.nix (for x86) It's bad to have the kernel config scattered across two places. (This should also be done for the other architectures.) Also, restore Xen and KVM guest support in Linux 3.10.
2013-08-01 14:01:59 +02:00
KSM y
${optionalString (!stdenv.is64bit) ''
HIGHMEM64G? y # We need 64 GB (PAE) support for Xen guest support.
''}
more kernel fixes
2014-11-11 09:21:53 +01:00
${optionalString (versionAtLeast version "3.9" && stdenv.is64bit) ''
kernel: Add more supported features
2014-11-08 11:44:19 +01:00
VFIO_PCI_VGA y
''}
VIRT_DRIVERS y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
# Media support.
${optionalString (versionAtLeast version "3.6") ''
MEDIA_DIGITAL_TV_SUPPORT y
MEDIA_CAMERA_SUPPORT y
MEDIA_RC_SUPPORT y
''}
${optionalString (versionAtLeast version "3.7") ''
MEDIA_USB_SUPPORT y
''}
# Our initrd init uses shebang scripts, so can't be modular.
${optionalString (versionAtLeast version "3.10") ''
BINFMT_SCRIPT y
''}
# Enable the 9P cache to speed up NixOS VM tests.
nixos: make several kernel common-config options optional Realistically, common-config is useful, but there are a lot of things in there that are non-optionally specified that aren't always useful. For example, when deploying grsecurity, I don't want the bluetooth, wireless, or input joystick/extra filesystem stack (XFS, etc), nor the staging drivers tree. The problem is that if you specify this in your own kernel config in the grsecurity module, by saying 'BT n' to turn off bluetooth, common-config turns on 'BT_HCIUART_BCSP y', which then becomes unused and errors out. This is really just an arbitrary picking at the moment, but it should be OK. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-18 00:30:51 +01:00
9P_FSCACHE? y
9P_FS_POSIX_ACL? y
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
linux: Enable transparent hugepages
2014-04-16 22:30:58 +02:00
# Enable transparent support for huge pages.
TRANSPARENT_HUGEPAGE? y
TRANSPARENT_HUGEPAGE_ALWAYS? n
TRANSPARENT_HUGEPAGE_MADVISE? y
linux: Enable FW_LOADER_USER_HELPER_FALLBACK We don't really need this anymore, except that our docs say that you can put firmware in /root/test-firmware, which doesn't work via /sys/module/firmware_class/parameters/path.
2014-10-20 13:18:33 +02:00
# zram support (e.g for in-memory compressed swap).
linux: Add support for zram
2014-04-24 14:03:18 +02:00
${optionalString (versionAtLeast version "3.4") ''
ZSMALLOC y
''}
ZRAM m
linux: Enable FW_LOADER_USER_HELPER_FALLBACK We don't really need this anymore, except that our docs say that you can put firmware in /root/test-firmware, which doesn't work via /sys/module/firmware_class/parameters/path.
2014-10-20 13:18:33 +02:00
Disable NFC on 3.17 or above This should only be temporary, but there's a bug in the 3.17 rc1 and rc2 that leads to cyclic module dependencies and a segfault during the build process.
2014-08-29 07:49:32 +02:00
${optionalString (versionAtLeast version "3.17") "NFC? n"}
linux: Add support for zram
2014-04-24 14:03:18 +02:00
linux: Enable FW_LOADER_USER_HELPER_FALLBACK We don't really need this anymore, except that our docs say that you can put firmware in /root/test-firmware, which doesn't work via /sys/module/firmware_class/parameters/path.
2014-10-20 13:18:33 +02:00
# Enable firmware loading via udev. Only needed for non-declarative
# firmware in /root/test-firmware.
${optionalString (versionAtLeast version "3.17") ''
FW_LOADER_USER_HELPER_FALLBACK y
''}
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
${kernelPlatform.kernelExtraConfig or ""}
${extraConfig}
''
Reference in a new issue Copy permalink