summaryrefslogtreecommitdiff
path: root/libre/linux-libre-64/PKGBUILD
AgeCommit message (Collapse)Author
2022-07-24wip - linux-libre-64bill-auger
2022-07-22sq - linux-libre-64bill-auger
2022-07-22sq - linux-libre-64bill-auger
2022-07-22sq - linux-libre-64bill-auger
2022-07-21linux-libre-64: added CONFIG_BATTERY_CW2015 optionIván Ávalos
2022-07-21wip - linux-libre-64 PKGBUILD from beeefcake filesystembill-auger
2022-07-21wip - linux-libre-64 PKGBUILD from local src pkgbill-auger
2022-07-21wip linux-libre-64bill-auger
2022-07-17finalize linux-libre-64bill-auger
2022-07-17sq - linux-libre-64bill-auger
2022-07-16sq - aarch64 cross compilerbill-auger
2022-07-16[linux-libre-64]: restrict build to armv7hbill-auger
2022-07-15[linux-libre-64]: cross-compile only from x86_64bill-auger
2022-07-15[linux-libre-64]: WIP - upgrade to v5.18.5Iván Ávalos
2022-04-06libre: linux-libre-64: Update to 5.15.12 by syncing with linux-libreDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-03-31treewide: Maintainer: GNUtoo: clarify the maintainer situationDenis 'GNUtoo' Carikli
The status quo is that any Parabola hacker is expected to (be able to) modify any packages, and having a single maintainer of a package discourages that practice as people would typically send a patch to the maintainer instead of pushing it directly. So for a start we can add common maintainership on package lacking any "Maintainer: " header for packages in repositories that are supposed to be maintained. As for finding who worked on a given package (in case it could be needed), the git log should have all the information. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-05-04libre: linux-libre-64: fix stripDenis 'GNUtoo' Carikli
Without that fix, on Parabola armv7h we have: | Stripping vmlinux... | strip: /build/linux-libre-64/pkg/linux-libre-64-headers/usr/lib/modules/5.11.11-gnu-2-64-ARCH/build/vmlinux: file format not recognized | ==> ERROR: A failure occurred in package_linux-libre-64-headers(). | Aborting... ==> Copying log and package files out of the chroot... And after entering the chroot again, running file on vmlinux in usr/lib/modules/5.11.11-gnu-2-64-ARCH/build/ in build/linux-libre-64/pkg/linux-libre-64-headers/ gives the following: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=61b2acea5733ab812f33e872c462a54e7e71fbeb, not stripped So the file is not recognized because we use the host strip instead of the cross compiler's strip. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-05-01libre: linux-libre-64: don't try to ship non-existing headersDenis 'GNUtoo' Carikli
Without that fix, when building for Parabola armv7h we have: | ==> Starting package_linux-libre-64-headers()... | Installing build files... | Installing headers... | cp: cannot stat 'arch/arm64/mach-dove/include': No such file or directory | ==> ERROR: A failure occurred in package_linux-libre-64-headers(). | Aborting... However these headers do exist for armv7h. As in this case we are building an aarch64 kernel, we don't need armv7h headers anyway. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-05-01linux-libre-64: update to 5.11.11 by syncing with linux-libreDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2021-02-09housekeepingbill-auger
2020-07-03kernels: SKIP local configurationDenis 'GNUtoo' Carikli
Instead of fixing checksums each time the kernel configuration is updated, we can simply skip them as they come from the same git repository than the PKGBUILD itself, so it should introduce any security issues. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-07-03kernels: Fix configuration checksumsDenis 'GNUtoo' Carikli
This regression was introduced by the following commits: 63359d4f8 kernels: re-enable the b43 and b43-legacy drivers 2e94284f5 kernels: re-enable the tg3 driver Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-07-03kernels: re-enable the b43 and b43-legacy driversDenis 'GNUtoo' Carikli
The b43 and b43-legacy drivers were removed because their corresponding upstream drivers loads a nonfree firmware. However linux-libre-firmware has a free firmware (ucode5.fw) that is used by both drivers. The b43 and b43-legacy driver are also typically enabled by Trisquel and Jason Self's linux-libre repository. Note that some kernel parameters like qos=0 might be necessary to make it work. This regression was introduced in linux-libre by the following commit: 32075365d upgpkg: libre/linux-libre 4.16.9_gnu-1 The drivers were added back by importing affected parts from the following upstream kernels and configurations: - config in linux-armv7 from Arch Linux ARM - config.i686 in linux from Arch Linux 32 - config from linux from Arch Linux Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-07-03kernels: re-enable the tg3 driverDenis 'GNUtoo' Carikli
The tg3 driver was removed because its upstream driver loads a nonfree firmware. However with linux-libre, the driver works fine without any nonfree firmware, at least on some computers like the HP NC6320. That driver is also typically enabled by Trisquel and Jason Self's linux-libre repository. This regression was introduced in linux-libre by the following commit: 32075365d upgpkg: libre/linux-libre 4.16.9_gnu-1 The following configuration: CONFIG_TIGON3=m CONFIG_TIGON3_HWMON=y is used in the following upstream kernels and configurations: - config in linux-armv7 from Arch Linux ARM - config.i686 in linux from Arch Linux 32 - config from linux from Arch Linux Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-06-20linux-libre-64: fix config.aarch64 checksumsDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-06-19linux-libre-64: sync with linux-libreDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-05-26libre: linux-libre-64: temporarily disable the chromebook packageDenis 'GNUtoo' Carikli
Note that even if it fixes packaging, in some case the compiler segfauls. In that case you need to restart the build until it succeddeds, which is usually around 1 or 2 times when you're unlucky. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-05-25libre: linux-libre-64: fix package_linux-libre-64-headersDenis 'GNUtoo' Carikli
Without that fix, we have the following issue: Removing documentation... cp: cannot stat 'arch/arm64/mach-dove/include': No such file or directory ==> ERROR: A failure occurred in package_linux-libre-64-headers(). Aborting... What is strange is that this error didn't appear when building linux-libre-64-5.6.12-1. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-05-24libre: linux-libre-64: enable 32bit compatibility for arm64Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-05-24libre: linux-libre-64: Fix image format for aarch64Denis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2020-05-22libre: add linux-libre-64 to replace archtecture specific versionsDenis 'GNUtoo' Carikli
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-21 21:00:08 +0000