Search Criteria
Package Details: linux-ck-headers 6.11.10-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-ck.git (read-only, click to copy) |
---|---|
Package Base: | linux-ck |
Description: | Headers and scripts for building modules for Linux-ck kernel |
Upstream URL: | https://wiki.archlinux.org/index.php/Linux-ck |
Licenses: | GPL-2.0-only |
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 459 |
Popularity: | 0.199022 |
First Submitted: | 2011-07-22 14:51 (UTC) |
Last Updated: | 2024-11-26 13:15 (UTC) |
Dependencies (11)
- linux-ckAUR
- pahole (pahole-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- libelf (elfutils-gitAUR) (make)
- pahole (pahole-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- xz (xz-gitAUR) (make)
Required by (8)
- ch343-dkms (optional)
- ch343ser-dkms-git (optional)
- ch9344ser-dkms-git (optional)
- e1000e-dkms (optional)
- fl2000-dkms (optional)
- i2c-ch341-dkms (optional)
- igb-dkms (optional)
- spi-config-dkms (optional)
Latest Comments
« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 308 Next › Last »
graysky commented on 2021-04-02 10:05 (UTC)
@Zalgo - 5.11.11-3 should fix this. See the forum thread for discussion: https://bbs.archlinux.org/viewtopic.php?pid=1965531
graysky commented on 2021-04-02 10:05 (UTC)
@artafinde - with some help, the native option now works with Intel and AMD. You will have to select the correct option though:
Zalgo commented on 2021-04-02 07:20 (UTC)
Thanks for the tip :) If i figure out a way to fix the PKGBUILD that doesn't require manual untarring I'll pose it here
graysky commented on 2021-04-01 20:20 (UTC)
That's odd. Makepkg doesn't seem to be untarring the patch. If you do it manually and add that to the source array, it works as expected.
Zalgo commented on 2021-04-01 17:26 (UTC)
This currently fails on my system with
can anyone else reproduce? I'll test in a clean chroot
graysky commented on 2021-03-07 19:38 (UTC)
@artafinde - I need to dig deeper, but I think it will be difficult to assign a native CPU out of some configs.
For example,
X86_INTEL_USERCOPY
config. I do that now but no other AMD chips are listed by upstream[1].Further, I believe AMD chips should not be in the
X86_P6_NOP
config[2] orX86_CMOV
config[3].https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L407
https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L421
https://github.com/graysky2/kernel_gcc_patch/blob/master/enable_additional_cpu_optimizations_for_gcc_v10.1%2B_kernel_v5.8%2B.patch#L438
artafinde commented on 2021-03-07 18:50 (UTC) (edited on 2021-03-07 18:50 (UTC) by artafinde)
@graysky checksum for the gcc kernel patch is failing - needs an update.
I noticed the changes in the patch repo and it mentions one should not use
native
on AMD chips. What's the reasoning behind this since the gcc 10 (and clang for what matters) can detect the cpu arch just fine:vp1981 commented on 2021-02-23 23:59 (UTC)
@simona, AFAIU, graysky keeps config sync with linux package and these two are in linux-zen but not yet in linux.
simona commented on 2021-02-21 23:19 (UTC)
ashmem_linux and binder_linux missing?
« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 308 Next › Last »