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/linux-rpi.nix

57 lines
1.9 KiB
Nix
Raw Normal View History

kernel: Enable cross compiling
2017-10-28 21:09:54 +02:00
{ stdenv, buildPackages, hostPlatform, fetchFromGitHub, perl, buildLinux, ... } @ args:
Adding linux-3.6-rpi I picked the change from https://github.com/aforemny/nixpkgs/commit/7b4d69eeff2eb10c395c8d1a52a0c1e246cddb45
2012-12-27 22:29:56 +01:00
raspberrypi-kernel: Updated to latest version as of 20130826 (rev 7849605f5a)
2013-08-27 12:05:13 +02:00
let
linux_rpi: 1.20171029 -> 1.20180417
2018-04-03 01:20:05 +02:00
modDirVersion = "4.14.34";
tag = "1.20180417";
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
in
kernel: buildLinux replaces import ./generic.nix - defined buildLinux as generic.nix instead of manual-config.nix. This makes kernel derivations a tad more similar to your typical derivations. - moved $buildRoot to within the source folder, this way it doesn't have to be created before the unpackPhase and make it easier to work on kernel source without running the unpackPhase
2018-01-28 19:50:18 +01:00
stdenv.lib.overrideDerivation (buildLinux (args // rec {
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
version = "${modDirVersion}-${tag}";
inherit modDirVersion;
Update the raspberry pi kernel to one newer.
2013-01-29 00:42:36 +01:00
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
src = fetchFromGitHub {
owner = "raspberrypi";
repo = "linux";
raspberrypifw, linux_rpi: 1.20161020 -> 1.20170303
2017-03-03 20:16:31 +01:00
rev = "raspberrypi-kernel_${tag}-1";
linux_rpi: 1.20171029 -> 1.20180417
2018-04-03 01:20:05 +02:00
sha256 = "1xgisvmcq50lpnd4rpqhaw52399n0rx2n8mp6k0bf8qm1g3vnza2";
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
};
Adding linux-3.6-rpi I picked the change from https://github.com/aforemny/nixpkgs/commit/7b4d69eeff2eb10c395c8d1a52a0c1e246cddb45
2012-12-27 22:29:56 +01:00
linux_rpi: Specify defconfig in kernel expression In particular, now the mainline kernel can be built on the RPi 1 as well (so kernelBaseConfig should always be a mainline defconfig from now on). And RPi 2 users can now use linux_rpi without doing the `nixpkgs.config.platform = lib.systems.platforms.raspberrypi2;` dance.
2017-11-03 14:50:19 +01:00
defconfig = {
"armv6l-linux" = "bcmrpi_defconfig";
"armv7l-linux" = "bcm2709_defconfig";
}.${stdenv.system} or (throw "linux_rpi not supported on '${stdenv.system}'");
linuxPackages: properly propagate `features` and `extraConfig` `kernel.override { features = ... }` didn't work before, now it works as expected.
2017-09-15 23:07:14 +02:00
features = {
efiBootStub = false;
} // (args.features or {});
Adding linux-3.6-rpi I picked the change from https://github.com/aforemny/nixpkgs/commit/7b4d69eeff2eb10c395c8d1a52a0c1e246cddb45
2012-12-27 22:29:56 +01:00
Set meta.hydraPlatforms instead of meta.platforms for some packages
2013-11-05 00:04:36 +01:00
extraMeta.hydraPlatforms = [];
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
})) (oldAttrs: {
postConfigure = ''
# The v7 defconfig has this set to '-v7' which screws up our modDirVersion.
sed -i $buildRoot/.config -e 's/^CONFIG_LOCALVERSION=.*/CONFIG_LOCALVERSION=""/'
'';
postFixup = ''
linux_rpi: More downstream device tree name fixups Also remove the upstream device trees beforehand so we don't accidentally end using them if we mess up in postFixup. Also on the topic of mess ups, make the copy unconditional since they always seem to be built on all architectures anyway so checking for their existence just hides typos.
2018-05-07 20:59:15 +02:00
# Make copies of the DTBs named after the upstream names so that U-Boot finds them.
# This is ugly as heck, but I don't know a better solution so far.
rm $out/dtbs/bcm283*.dtb
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
copyDTB() {
linux_rpi: More downstream device tree name fixups Also remove the upstream device trees beforehand so we don't accidentally end using them if we mess up in postFixup. Also on the topic of mess ups, make the copy unconditional since they always seem to be built on all architectures anyway so checking for their existence just hides typos.
2018-05-07 20:59:15 +02:00
cp -v "$out/dtbs/$1" "$out/dtbs/$2"
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
}
linux_rpi: More downstream device tree name fixups Also remove the upstream device trees beforehand so we don't accidentally end using them if we mess up in postFixup. Also on the topic of mess ups, make the copy unconditional since they always seem to be built on all architectures anyway so checking for their existence just hides typos.
2018-05-07 20:59:15 +02:00
copyDTB bcm2708-rpi-0-w.dtb bcm2835-rpi-zero.dtb
copyDTB bcm2708-rpi-0-w.dtb bcm2835-rpi-zero-w.dtb
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02:00
copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-a.dtb
copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-b.dtb
copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-b-rev2.dtb
copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-a-plus.dtb
copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-b-plus.dtb
copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-zero.dtb
copyDTB bcm2708-rpi-cm.dtb bcm2835-rpi-cm.dtb
copyDTB bcm2709-rpi-2-b.dtb bcm2836-rpi-2-b.dtb
copyDTB bcm2710-rpi-3-b.dtb bcm2837-rpi-3-b.dtb
linux_rpi: More downstream device tree name fixups Also remove the upstream device trees beforehand so we don't accidentally end using them if we mess up in postFixup. Also on the topic of mess ups, make the copy unconditional since they always seem to be built on all architectures anyway so checking for their existence just hides typos.
2018-05-07 20:59:15 +02:00
copyDTB bcm2710-rpi-3-b-plus.dtb bcm2837-rpi-3-b-plus.dtb
copyDTB bcm2710-rpi-cm3.dtb bcm2837-rpi-cm3.dtb
linux-rpi: 4.1.20-XXX -> 4.4.13-1.20160620-1 - Add a patch to unset CONFIG_LOCALVERSION in the v7 build. - Copy all the device trees to match the upstream names so U-Boot can find them. (This is a hack.)
2016-07-04 00:50:37 +02: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
})
Reference in a new issue Copy permalink