summaryrefslogtreecommitdiffstats
path: root/meta-networking/recipes-kernel
Commit message (Collapse)AuthorAgeFilesLines
* [dunfell] wireguard: Upgrade to 1.0.20220627 (module) and 1.0.20210914 (tools)Colin Finck2022-10-305-93/+25
| | | | | | | | | | | | Quoting Jason A. Donenfeld on IRC: <zx2c4> Colin_Finck: you should never, ever use old versions <zx2c4> Notice that neither the major nor minor version numbers change <zx2c4> Use the latest versions on your LTS With that definite answer, I'd like to fix the problem described in https://lore.kernel.org/yocto/CswA.1659543156268567471.pbrp@lists.yoctoproject.org/ by importing the latest versions instead of maintaining our own fork of wireguard 1.0.20200401. Signed-off-by: Armin Kuster <akuster808@gmail.com>
* recipes: Update SRC_URI branch and protocolsArmin Kuster2021-11-172-2/+2
| | | | | | | | This patch updates SRC_URIs using git to include branch=master if no branch is set and also to use protocol=https for github urls as generated by the conversion script in OE-Core. Signed-off-by: Armin Kuster <akuster808@gmail.com>
* wireguard: fix build issue with updated 5.4 kernelArmin Kuster2021-04-072-1/+34
| | | | | | | | error: static declaration of 'icmp_ndo_send' follows non-static declaration | 959 | static inline void icmp_ndo_send(struct sk_buff *skb_in, int type, int code, __be32 info) | | ^~~~~~~~~~~~~ Signed-off-by: Armin Kuster <akuster808@gmail.com>
* wireguard-module: remove PKG assignmentMartin Jansa2021-02-101-7/+0
| | | | | | | | | | | | | | | * it's not clear why it was added in first place and it's causing issues since: "package: get_package_mapping: avoid dependency mapping if renamed package provides original name" commit in oe-core as discussed in: https://lists.openembedded.org/g/openembedded-core/message/143672 https://github.com/openembedded/meta-openembedded/issues/285 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> (cherry picked from commit 304f660f880bdf7dd5c51695875ab0a73aaed8b2) Signed-off-by: Armin Kuster <akuster808@gmail.com> (cherry picked from commit f9502868169715ee4945f5d8bef7c845dbb7b9e0) Signed-off-by: Armin Kuster <akuster808@gmail.com>
* wireguard-module: fix build issue with 5.4 kernelArmin Kuster2020-12-242-1/+31
| | | | | | | | | | | | | | | | | | | /tmp/work/qemux86_64-poky-linux/wireguard-module/1.0.20200401-r0/git/src/compat/compat-asm.h:44: warning: "SYM_FUNC_START" redefined | 44 | #define SYM_FUNC_START ENTRY | | | In file included from /tmp/work/qemux86_64-poky-linux/wireguard-module/1.0.20200401-r0/git/src/compat/compat-asm.h:9, | from <command-line>: | /tmp/work-shared/qemux86-64/kernel-source/include/linux/linkage.h:218: note: this is the location of the previous definition | 218 | #define SYM_FUNC_START(name) \ | | | In file included from <command-line>: | /tmp/work/qemux86_64-poky-linux/wireguard-module/1.0.20200401-r0/git/src/compat/compat-asm.h:45: warning: "SYM_FUNC_END" redefined | 45 | #define SYM_FUNC_END ENDPROC | | Backporit fix from upstream Signed-off-by: Armin Kuster <akuster808@gmail.com>
* wireguard: Upgrade to latest compat external module and toolsKhem Raj2020-04-073-8/+7
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard-tools: Ensure make clean target is run properlyKhem Raj2020-03-291-5/+4
| | | | | | | | | When S is pointing to a level up, it calls clean target which also tries to clean the module build objects, which causes make clean to misnehave since the env is not set to build module and it tries to reach out to /lib/modules dir on host Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: Upgrade to 20191219 snapshotKhem Raj2020-01-293-2/+2
| | | | | | Fixes build with kernel >= 5.4 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: Upgrade 20190905 to 20190913Scott Ellis2019-09-153-2/+2
| | | | | Signed-off-by: Scott Ellis <scott@jumpnowtek.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: Upgrade 20190702 to 20190905Scott Ellis2019-09-073-2/+2
| | | | | Signed-off-by: Scott Ellis <scott@jumpnowtek.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: Upgrade 20190406 to 20190702Scott Ellis2019-08-043-2/+2
| | | | | Signed-off-by: Scott Ellis <scott@jumpnowtek.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: Upgrade 20190123 -> 20190406Scott Ellis2019-05-203-2/+2
| | | | | | | Fixes issues with kernels 5.1 and greater. Signed-off-by: Scott Ellis <scott@jumpnowtek.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: udpate to 20190123 versionStefan Agner2019-01-303-2/+2
| | | | | Signed-off-by: Stefan Agner <stefan.agner@toradex.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: use ${nonarch_base_libdir} for modulesStefan Agner2019-01-301-2/+2
| | | | | | | | Use ${nonarch_base_libdir} for modules. This makes this recipe working also when using usrmerge. Signed-off-by: Stefan Agner <stefan.agner@toradex.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* wireguard: udpate to 20171221 versionArmin Kuster2018-03-053-2/+2
| | | | | | | | | | | | this fixes build issue on a 4.14 kernel: /src/compat/padata/padata.c:831:9: error: implicit declaration of function 'padata_alloc'; did you mean 'padata_alloc_pd'? [-Werror=implicit-function-declaration] | return padata_alloc(wq, cpu_possible_mask, cpu_possible_mask); | ^~~~~~~~~~~~ | padata_alloc_pd Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* wireguard: Upgrade to 20170810 snapshotKhem Raj2017-09-123-3/+2
| | | | | | | | Fixes build with linux kernel 4.12+ Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* wireguard-tools: Add bash to rdepsKhem Raj2017-09-121-1/+1
| | | | | | | | | | Fixes QA error /usr/bin/wg-quick contained in package wireguard-tools requires /bin/bash Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* recipes: remove blacklisted recipesMartin Jansa2017-08-315-276/+0
| | | | | | | | * as PNBLACKLIST message says, these recipes are blacklisted for long time and nobody showed any interest to fix them * remove all unused .patch and .inc files as well Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* wireguard: bump version to latest snapshot 0.0.20170517Stefan Agner2017-06-283-2/+2
| | | | | | | Use the latest available snapshot 0.0.20170517 of WireGuard. Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* wireguard: module install cleanupJoe MacDonald2017-05-091-6/+14
| | | | | | | The module_install target shouldn't be used, just installing the module to the sysroot directly seems more appropriate. Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* wireguard: blacklistJoe MacDonald2017-05-011-0/+2
| | | | Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* wireguard: add dependencies and kernel build optionsJoe MacDonald2017-04-271-2/+10
| | | | Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* wireguard: add WireGuard kernel module and toolsStefan Agner2017-04-273-0/+58
| | | | | | | | | | | | | | | | | | | | 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. The recipes add the current experimental snapshot v0.0.20170421 out-of-tree kernel module and tools. The kernel module has some kernel configuration dependencies such as some configuration part of features/netfilter/netfilter.scc, hence netfilter.scc should be part of KERNEL_EXTRA_FEATURES (which is the case by default). Since wireguard-tools is TUNE_PKGARCH and depends on wireguard-module which is MACHINE_ARCH (like all kernel modules) we need to add this dependency to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS. Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* recipes: add removal date to PNBLACKLIST messagesMartin Jansa2017-04-052-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | * based on discussion in pndeprecated thread: https://patchwork.openembedded.org/patch/137573/ update the messages to warn possible users that the recipe will be removed before the end of the next development cycle (before Yocto 2.4 is released). * updated with: sed -i 's/^\(PNBLACKLIST.*".*\)"/\1 - the recipe will be removed on 2017-09-01 unless the issue is fixed"/g' `git grep PNBLACKLIST | sed 's/:.*//g' | sort -u | xargs` * then noticed couple recipes being blacklisted only based on DISTRO_FEATURES, so removed those: meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb meta-oe/recipes-connectivity/bluez/bluez-hcidump_2.5.bb meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb meta-oe/recipes-connectivity/bluez/gst-plugin-bluetooth_4.101.bb meta-oe/recipes-navigation/foxtrotgps/foxtrotgps_1.1.1.bb meta-oe/recipes-navigation/gypsy/gypsy.inc meta-oe/recipes-navigation/navit/navit.inc meta-oe/recipes-support/opensync/libsyncml_0.5.4.bb * if it isn't fixed by this date, it's fair game to be removed whenever someone gets around to i Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* remove True option to getVar callsJoshua Lock2016-12-021-3/+3
| | | | | | | | | getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
* iscsitarget,netmap-moduls,vboxguestdrivers: Blacklist, not compatible with ↵Martin Jansa2016-09-151-0/+3
| | | | | | default kernel version 4.8 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* netmap: blacklistMartin Jansa2016-07-071-0/+3
| | | | | | | * it's broken for very long time Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* netmap-modules: Avoid type warning with python v3Richard Purdie2016-06-081-1/+1
| | | | | | | Python 3 is stricter about type comparisions, this avoids warnings. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Revert "netmap-modules: Modules may not have the same arch as userspace"Joe MacDonald2016-03-031-5/+0
| | | | | | This reverts commit b49d08411c75a8fec8ad591105b324a6766aa8d5. Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* netmap-modules: fix build with kernel < 3.17Martin Jansa2016-01-141-1/+7
| | | | | | | * define NETMAP_LINUX_ALLOC_NETDEV_4ARGS only when MACHINE is using kernel 3.17 or newer Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* netmap-modules: Modules may not have the same arch as userspaceJackie Huang2015-11-301-0/+5
| | | | | | | | | | Kernel modules may not have the same architecture as user space. So we tell INSANE_SKIP to skip checking the arch for the modules. This is consistent with other kernel modules and the kernel recipe. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* netmap-modules: make deterministic builds for driversJackie Huang2015-11-301-1/+25
| | | | | | | | | | | | | | | | | | | The driver builds are optional, but for deterministic builds, we should should be able to explicitly enable/disable the builds for them in a proper place (maybe in BSP). But we can't use PACKAGECONFIG since there is no option for each driver, and the options are: --no-drivers do not compile any driver --no-drivers= do not compile the given drivers (comma sep.) --drivers= only compile the given drivers (comma sep.) So use NETMAP_DRIVERS to list the needed drivers and add proper configs to EXTRA_OECONF, the default is no drivers, and all supported drivers are listed in NETMAP_ALL_DRIVERS. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* netmap-modules: disable building virtio_net driversMartin Jansa2015-11-161-1/+1
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* netmap: set MACHINE_ARCH, because it depends on MACHINE_ARCH netmap-modulesMartin Jansa2015-11-161-2/+1
| | | | | | | | | | | | | | | | | * it's also using MACHINE specific variables like: STAGING_KERNEL_DIR. STAGING_KERNEL_BUILDDIR * drop suspicious: do_fetch[depends] += "netmap-modules:do_fetch" fetcher should use .lock files to prevent updating the same repository in parallel * see: http://lists.openembedded.org/pipermail/openembedded-devel/2015-September/103271.html * fixes: ERROR: netmap different signature for task do_configure.sigdata between qemux86copy and qemux86 basehash changed from 748eae270193023d79f7d6a69aa1b8d2 to 9267873ef5fa4474d5f60fc79044ab64 Variable MACHINE value changed from 'qemux86copy' to 'qemux86' Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* netmap-modules: fix compilation failureQi.Chen@windriver.com2015-10-211-0/+2
| | | | | | | | | | | | | | | | | | | | | If CONFIG_IXGBE is enabled in kernel. This package fails to build with error messages like below. | #error "unsupported ixgbe driver version" | ^ ....... error: request for member 'count' in something not a structure or union | na.num_rx_desc = NM_IXGBE_RX_RING(adapter, 0)->count; | ^ | cc1: some warnings being treated as errors Fix this problem by disabling igxbe driver in netmap-modules. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>
* netmap: add new packageArmin Kuster2015-09-155-0/+239
this adds netmap, the fast packet I/O framework http://info.iet.unipi.it/~luigi/netmap/ - updated to latest version to get kernel 4.1 support - fixed printf type issue - Fixed manual config options Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com>