| Age | Commit message (Collapse) | Author |
|
Enable "make mrproper" before packaging kernel source tarball. After enabling
PWRU support in T8496, the auto-generated kernel source tarball grew from under
1 GB to ~4 GB, largely due to intermediate build artifacts (for example,
vmlinuz.o growing from 54 MB to 618 MB with additional debug symbols).
Since the tarball is intended to contain kernel sources and custom patches and
not intermediate objects, we now clean the tree with "make mrproper" before
creating the tarball. This keeps package size down while preserving
rebuildability.
|
|
Instead of one build function per driver (ixgbe, i40, ice) which will anyways
result in the same Python code path to be executed - use one common helper
name: build_intel_nic
|
|
The current version of the Intel ice driver does not compile with a recent
LTS Kernel due to missing internal Kernel API adjustments in the Intel driver.
This commit contains custom patches to make the driver build.
|
|
The current version of the Intel i40e driver does not compile with a recent
LTS Kernel due to missing internal Kernel API adjustments in the Intel driver.
This commit contains custom patches to make the driver build.
|
|
* Forwared port all out-of-tree driver patches
* Add Intel QAT patch to make it compile for LInux 6.18
* Remove out-of-tree OpenVPN DCO module - now available upstream
|
|
|
|
If build.py detects a local "linux" directory which could be a
Git repository - it is used over downloading the released tarball.
|
|
T7857: Add Realtek RTL8126 5Gbit driver
|
|
Signed-off-by: Thomas Kupper <thomas.kupper@gmail.com>
|
|
Remove the `accel-ppp` from the packages, as we migrated to the
`accel-ppp-ng` and do not need it anymore.
Remove build scripts and patches.
|
|
|
|
Exclude auxiliary directories from linux-kernel and related to
linux-kernel tarballs
|
|
* T7666: Add vpp-sflow src patches and accel-ppp-ng to gitignore
* T7666: Add script to build accel-ppp-ng binaries
* Update scripts/package-build/linux-kernel/build-accel-ppp-ng.sh
---------
Co-authored-by: Daniil Baturin <daniil@baturin.org>
|
|
|
|
|
|
The build package binaries script should exit if the repo is absent
or cannot be cloned
If a build package `repo-a` depends on the `repo-b` and the `repo-b`
cannot be cloned, then we shoud exit from the script to avoid
partly build dependencies
For example:
```
[[packages]]
name = "fake-repo"
commit_id = "v0.0.1"
scm_url = "https://github.com/vyos/fake-repo"
[[packages]]
name = "ethtool"
commit_id = "debian/1%6.10-1"
scm_url = "https://salsa.debian.org/kernel-team/ethtool"
```
If ethtool depends on some fake-package and this package cannot be
downloaded from the repo, then we shouldn't build the ethtool package
at all.
|
|
Move the Kernel build dependencies to package.toml to unbload the build
container even more.
|
|
|
|
Use one build script to rule all the Intel Git based drivers.
|
|
Previous commit a10b29560 ("intel: T6847: update IXGBE Out-Of-Tree driver to
v6.0.5") missed a proper CI "git clone" on the driver repository - this has
been fixed.
|
|
Build tarballs for the packages related linux-kernel dir.
|
|
We need to sign the module during the Debian build run, before the
binaries are packed into the resulting DEB.
|
|
|
|
|
|
The shim review board (which is the secure boot base loader) recommends using
ephemeral keys when signing the Linux Kernel. This commit enables the Kernel
build system to generate a one-time ephemeral key that is used to:
* sign all build-in Kernel modules
* sign all other out-of-tree Kernel modules
The key lives in /tmp and is destroyed after the build container exits and is
named: "VyOS build time autogenerated kernel key".
In addition the Kernel now uses CONFIG_MODULE_SIG_FORCE. This now makes it
unable to load any Kernel Module to the image that is NOT signed by the
ephemeral key.
|
|
Get kernel version from the vyos-build/data/defaults.toml
for buld 'linux-kernel' and related packages
Retrun the original build-jool.py script
|
|
Add build scripts for .deb packages without Jenkins.
To exclude Jenkins we need some place where we can put new builds-scripts
to run in parallel (old/new) during meantime
We will deprecate old Jenkins package builds in the future.
|