created | 2024-08-05T03:18:00Z |
---|---|
begin | 2024-07-30T00:00:00Z |
end | 2024-07-31T00:00:00Z |
path | src/sys |
commits | 5 |
date | 2024-07-30T05:57:31Z | |||
---|---|---|---|---|
author | guenther | |||
files | src/sys/sys/cdefs.h | log | diff | annotate |
message |
Recognize the features defines for POSIX 1003.1-2024, giving new values for __POSIX_VISIBLE and __XPG_VISIBLE. ok millert@ |
date | 2024-07-30T08:59:33Z | |||
---|---|---|---|---|
author | kettenis | |||
files | src/sys/arch/arm64/arm64/cpu.c | log | diff | annotate |
src/sys/arch/arm64/include/armreg.h | log | diff | annotate | |
message |
Populate most of the remaining hwcap and hwcap2 flags based on the detected CPU features. ok naddy@ |
date | 2024-07-30T13:41:15Z | |||
---|---|---|---|---|
author | yasuoka | |||
files | src/sys/net/if_pppx.c | log | diff | annotate |
message |
Exports the statistics when PIPEXDSESSION. Found by ymatsui at iij. ok mvs |
date | 2024-07-30T19:47:05Z | |||
---|---|---|---|---|
author | mglocker | |||
files | src/sys/arch/arm64/conf/GENERIC | log | diff | annotate |
src/sys/arch/arm64/conf/RAMDISK | log | diff | annotate | |
message |
Make the Samsung Galaxy Book4 Edge (x1e80100) boot in ACPI mode; Until now the kernel did panic during early boot because we couldn't respond to the battery requests sent to the 0xa1 "bus". This (dummy) driver registers a 0xa1 region space very early, and responds with a static zero value to satisfy the battery requests on 0xa1, which let us boot successfully to multi-user. In the future this machine should be operated in FDT mode, and an improved AML parsing interface might make this workaround obsolete also for RAMDISK. Help and OK kettenis@, deraadt@ |
date | 2024-07-30T19:47:06Z | |||
---|---|---|---|---|
author | mglocker | |||
files | src/sys/dev/acpi/acpi.c | log | diff | annotate |
src/sys/dev/acpi/acpisectwo.c | log | diff | annotate | |
src/sys/dev/acpi/files.acpi | log | diff | annotate | |
message |
Make the Samsung Galaxy Book4 Edge (x1e80100) boot in ACPI mode; Until now the kernel did panic during early boot because we couldn't respond to the battery requests sent to the 0xa1 "bus". This (dummy) driver registers a 0xa1 region space very early, and responds with a static zero value to satisfy the battery requests on 0xa1, which let us boot successfully to multi-user. In the future this machine should be operated in FDT mode, and an improved AML parsing interface might make this workaround obsolete also for RAMDISK. Help and OK kettenis@, deraadt@ |