| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
required
Sometimes the defconfig and the source code are out of sync, this
can result in issues like this one:
| ==> Starting build()...
| scripts/kconfig/conf --syncconfig Kconfig
| *
| * Restart config...
| *
| *
| * General architecture-dependent options
| *
| OProfile system profiling (OPROFILE) [M/n/y/?] m
| OProfile multiplexing support (EXPERIMENTAL) (OPROFILE_EVENT_MULTIPLEX) [N/y/?] n
| Kprobes (KPROBES) [Y/n/?] y
| Optimize very unlikely/likely branches (JUMP_LABEL) [Y/n/?] y
| Static key selftest (STATIC_KEYS_SELFTEST) [N/y/?] n
| Stack Protector buffer overflow detection (STACKPROTECTOR) [Y/n/?] (NEW)
This makes sure that in such case, the default choice is used instead of
asking the user about it.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
While updating this kenrel to 5.1.3-gnu, the 5.0.2-gnu defconfig
was accidentally commited.
This change fixes it by importing linux-libre's defconfig for
x86_64.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The previous PKGBUILD was build and tested.
However I removed the following files after testing
and forgott to regenrate the sha512sum:
'kernel.its', 'kernel.keyblock', 'kernel_data_key.vbprivk'
I didn't re-test after that since it already took hours to
build it my build machine and that this PKGBUILD is based
on a well tested PKGBUILD.
I didn't bump the package revision in this commit because the
package cound't build before.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
With this kernel, on machines with an x86_64 compatible CPU, you
can run an i686 userspace with an x86_64 kernel.
This for instance enables to use the same i686 rootfs on computers
with 32bit and 64bit CPUs, while still being able to take advantage
of a 64bit kernel on the machines that supports it.
The users will then need to force i686 in pacman.conf like that:
[options]
Architecture = i686
They will also need to select the right kernel at boot.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
