created | 2024-10-13T02:26:41Z |
---|---|
begin | 2024-10-10T00:00:00Z |
end | 2024-10-11T00:00:00Z |
path | src/sys |
commits | 8 |
date | 2024-10-10T00:30:34Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/agpvar.h | log | diff | annotate |
message | remove unused struct agp_memory_info |
date | 2024-10-10T00:41:01Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/agpvar.h | log | diff | annotate |
message | remove unused defines |
date | 2024-10-10T03:36:10Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/agp_i810.c | log | diff | annotate |
src/sys/dev/pci/agpvar.h | log | diff | annotate | |
message | remove unused agp_softc variables |
date | 2024-10-10T05:51:23Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/arch/amd64/pci/acpipci.c | log | diff | annotate |
message |
allow MSI with the QEMU default pc-i440fx machine This makes it possible to use MSI for virtual functions of Intel network devices without having to specify the q35 machine. QEMU is detected by testing for the Qumranet pci subsystem vendor id, suggested by sf@. MSI previously wasn't enabled as i440fx models a machine from 1996 with ACPI 1.0, and MSI is only enabled for ACPI >= 2.0. Initial patch from Yuichiro NAITO. ok yasuoka@ sf@ |
date | 2024-10-10T06:00:42Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/arch/i386/pci/pci_machdep.c | log | diff | annotate |
message |
allow MSI with the QEMU default pc-i440fx machine This makes it possible to use MSI for virtual functions of Intel network devices without having to specify the q35 machine. QEMU is detected by testing for the Qumranet pci subsystem vendor id, suggested by sf@. MSI previously wasn't enabled as 82441FX is in the list of excluded devices. Initial patch from Yuichiro NAITO. ok yasuoka@ sf@ |
date | 2024-10-10T06:50:58Z | |||
---|---|---|---|---|
author | dlg | |||
files | src/sys/net/if_tun.c | log | diff | annotate |
message |
neuter the tun/tap ioctls that try and modify interface flags. historically there was just tun(4) that supported both layer 3 p2p and ethernet modes, but had to be reconfigured at runtime by userland to properly change the interface type and interface flags. this is obviously not a great idea, mostly because a lot of stack behaviour around address management makes assumptions based on these parameters, and changing them at runtime confuses things. splitting tun so ethernet was handled by a specific tap(4) driver was a first step at locking this down. this takes a further step by restricting userlands ability to reconfigure the interface flags, specifically IFF_BROADCAST, IFF_MULTICAST, and IFF_POINTOPOINT. this change lets userland pass those values via the ioctls, but only if they match the current set of flags on the interface. these flags are set appropriate for the type of interface when it's created, but should not be changed afterwards. nothing in base uses these ioctls, so the only fall out will be from ports doing weird things. ok claudio@ kn@ |
date | 2024-10-10T19:33:05Z | |||
---|---|---|---|---|
author | miod | |||
files | src/sys/arch/alpha/alpha/locore.s | log | diff | annotate |
src/sys/arch/alpha/alpha/locore0.S | log | diff | annotate | |
message |
Remove the gazillion of macros to get fields from curcpu(), and use relative addressing from the register holding the value of curcpu() instead. No functional change, but shaves a few bytes of code on MULTIPROCESSOR kernels. |
date | 2024-10-10T23:15:27Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/fdt/qccpu.c | log | diff | annotate |
message | remove unused struct cpu_freq_tbl |