74a865b1fc
The reason why the external wireguard kernel module is not allowed with kernel headers >= 5.6 is that wireguard is included in the upstream kernel since 5.6 rather than some kind of (fixable) incompatibility issue. Adjust the comment to make that clear. While we're at it, drop the redundant !5.6 dependency on the kernel headers dependency comment. If headers are older than 3.10, then they are also older than 5.6, so the statement is redundant. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
27 lines
1 KiB
Plaintext
27 lines
1 KiB
Plaintext
config BR2_PACKAGE_WIREGUARD_LINUX_COMPAT
|
|
bool "wireguard linux-compat"
|
|
depends on BR2_LINUX_KERNEL
|
|
# kernel module requires 3.10+
|
|
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
|
|
# kernel module in upstream linux since 5.6
|
|
depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_6
|
|
help
|
|
WireGuard is an extremely simple yet fast and modern VPN
|
|
that utilizes state-of-the-art cryptography. It aims to be
|
|
faster, simpler, leaner, and more useful than IPSec, while
|
|
avoiding the massive headache. It intends to be considerably
|
|
more performant than OpenVPN. WireGuard is designed as a
|
|
general purpose VPN for running on embedded interfaces and
|
|
super computers alike, fit for many different
|
|
circumstances.
|
|
|
|
Support for WireGuard is included in Linux 5.6+. This
|
|
package provides a backport of the kernel support for older
|
|
kernels.
|
|
|
|
https://www.wireguard.com
|
|
|
|
comment "wireguard-linux-compat needs a toolchain w/ headers >= 3.10"
|
|
depends on BR2_LINUX_KERNEL
|
|
depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
|