4e75a31e98
As per the in-line comment, this is where distros should configure it. Not via kernel command line parameters. As found by looking at the implementation, while exploring the cause of a bug on the Raspberry Pi 4, it was found that `cma=` on the command line parameters will overwrite the values a device tree will have configured for a given platform. With this, the more recent 5.4 vendor kernel boots just fine on the Raspberry Pi 4 using our common configuration. |
||
---|---|---|
.. | ||
channel.nix | ||
installation-cd-base.nix | ||
installation-cd-graphical-base.nix | ||
installation-cd-graphical-gnome.nix | ||
installation-cd-graphical-plasma5-new-kernel.nix | ||
installation-cd-graphical-plasma5.nix | ||
installation-cd-minimal-new-kernel.nix | ||
installation-cd-minimal.nix | ||
iso-image.nix | ||
sd-image-aarch64-new-kernel.nix | ||
sd-image-aarch64.nix | ||
sd-image-armv7l-multiplatform.nix | ||
sd-image-raspberrypi4.nix | ||
sd-image-raspberrypi.nix | ||
sd-image.nix | ||
system-tarball-fuloong2f.nix | ||
system-tarball-pc-readme.txt | ||
system-tarball-pc.nix | ||
system-tarball-sheevaplug.nix | ||
system-tarball.nix |