summaryrefslogtreecommitdiff
path: root/sys/external/bsd
AgeCommit message (Collapse)Author
2023-06-24Fix typo in comment.msaitoh
2023-06-03adapt to ${CC_WNO_MAYBE_UNINITIALIZED}lukem
Use ${CC_WNO_MAYBE_UNINITIALIZED} instead of the older style more complex expressions. Remove workarounds if they were for a specific version of gcc < 10.
2023-06-03adapt to ${CC_WNO_IMPLICIT_FALLTHROUGH}lukem
Use ${CC_WNO_IMPLICIT_FALLTHROUGH} instead of the older style more complex expressions.
2023-05-25amdgpu: Fix mostly harmless merge botch.riastradh
Avoids confusing error message that should have been confined to an error branch.
2023-05-22Use the offset in mmap calculations.nat
It fixes wsfb(4) when used with intelfb(4). Ok riastradh@ XXX pullup-10
2023-05-12i915: Avoid dereferencing null fence if resv has changed.riastradh
PR kern/57402 XXX pullup-10
2023-05-07RISC-V support that works on QEMU with a single hart.skrll
Thanks for Simon Burge for plic(4).
2023-05-01drm: KASSERT(A && B) -> KASSERT(A); KASSERT(B)riastradh
2023-04-09dwc2: KASSERT(A && B) -> KASSERT(A); KASSERT(B)riastradh
2023-03-07remove "nouveau" from a comment. noted by jmcneill.mrg
2023-03-07radeon: Kick out genfb on firmware framebuffer before initializing.mrg
this is the same change as nouveau_pci.c:1.37, and should fix at least PR#56714 and i thought at least another PR i can't find right now. it fixes at least 2 different radeon cards for me on UEFI booted system. XXX: pullup-10 also include the original change: http://mail-index.netbsd.org/source-changes/2023/03/01/msg143606.html
2023-03-01nouveau: Kick out genfb on firmware framebuffer before initializing.riastradh
PR kern/53126
2023-03-01amdgpu: Fix bogus loop invariant assertions in amdgpu_gart_map.riastradh
2023-02-25linux asm/barrier.h: Fix !MULTIPROCESSOR build.riastradh
2023-02-24drm: Eliminate __HAVE_ATOMIC_AS_MEMBAR conditionals.riastradh
Discussed on tech-kern: https://mail-index.netbsd.org/tech-kern/2023/02/23/msg028729.html
2023-02-21drm: Teach dmabuf to handle lseek.riastradh
Needed by libdrm_amdgpu. Based on patch from Jeff Frasca -- thanks! XXX pullup-10
2023-02-21amdgpu: Fix scale factor for 64-bit doorbell indexing.riastradh
The register is 64 bits wide, but the indexing is for 32-bit quantities (and presumably index must be even here). Found by Jeff Frasca -- thanks!
2023-02-03Fix use after free on packet with broken lengthschristos
Under the scenario with a packet with length of 67 bytes, a header length using the default of 20 bytes and a TCP data offset (th_off) of 48 will cause m_pullup() to fail to make sure bytes are arranged contiguously. m_pullup() will free the mbuf chain and return a null. ipfilter stores the resultant mbuf address (or the resulting NULL) in its fr_info_t structure. Unfortunately the erroneous packet is not flagged for drop. From FreeBSD via CY Schubert; originally reported by: Robert Morris <rtm at lcs.mit.edu>
2022-12-26remove the PPP HDLC ioctls from more copies of sanitizers.chs
2022-12-10merge acpica 20220331 to 20221020christos
2022-12-10Import acpica 2022-10-20christos
20 October 2022. Summary of changes for version 20221020: This release is available at https://acpica.org/downloads 0) Global changes: Allow disabling of -Werror. For distro maintainers having `-Werror` can delay update of GCC. Since every GCC release might add new warnings that were not yet captured, it might break the build of packages. With this change, distros can now build with `NOWERROR=TRUE` instead of patching either the errors or the makefiles. The default behavior keeps on using `-Werror`. 1) ACPICA kernel-resident subsystem: Added support for FFH Operation Region special context data. FFH(Fixed Function Hardware) Opregion is approved to be added in ACPI 6.5 via code first approach[1]. It requires special context data similar to GPIO and Generic Serial Bus as it needs to know platform specific offset and length. Reverted this commit "executer/exsystem: Warn about sleeps greater than 10 ms." Due to user complaints about valid sleeps greater than 10ms seen in some existing machines -- generating lots of warnings. Do not touch VGA memory when EBDA < 1KiB. The ACPICA code assumes that EBDA region must be at least 1KiB in size. Because this is not guaranteed, it might happen that while scanning the memory for RSDP pointer, the kernel touches memory above 640KiB. This is unwanted as the VGA memory range may not be decoded or even present when running under virtualization. Check that EBDA pointer is in valid memory. If the memory at 0x40e is uninitialized, the retrieved physical memory address of EBDA may be beyond the low memory (i.e. above 640K). If so, the kernel may unintentionally access the VGA memory, that might not be decoded or even present in case of virtualization. 2) iASL Compiler/Disassembler and ACPICA tools: Completed the existing partial support for the CDAT "table". Although this isn't technically an ACPI table (It doesn't go into the XSDT), it is possible to support this table in the Data Table compiler. Created one new file, "utilities/utcksum.c", used to centralize checksum generation/validation into one location. Includes changes to makefiles and MSVC project files. Updated support for the IORT table - update to version E.e Added CXL 3.0 structures (CXIMS & RDPAS) to the CEDT table iASL: Added CCEL table to both compiler/disassembler. iASL: NHLT table: Fixed compilation of optional undocumented fields iASL: Fix iASL compile error due to ACPI_TDEL_OFFSET. Commit # 10e4763 ("iASL: Add CCEL table to both compiler/disassembler") introduced the iASL build issue. The issue is due to using ACPI_TDEL_OFFSET for CCEL table member reference. To fix it, change ACPI_TDEL_OFFSET with ACPI_CCEL_OFFSET.
2022-12-07exsystem.c: revert ACPI warning about sleep values >10msgutteridge
acpica 20220331 introduced the following change: For the ASL Sleep() operator, issue a warning if the sleep value is greater than 10 Milliseconds. Quick boottime is important, so warn about sleeps greater than 10 ms. Distribution Linux kernels reach initrd in 350 ms, so excessive delays should be called out. 10 ms is chosen randomly, but three of such delays would already make up ten percent of the boottime. This can generate many console messages like: [ 26.055036] ACPI Warning: Firmware issue: Excessive sleep time (0x0000000000000064 ms > 10 ms) in ACPI Control Method (20220331/exsystem-239) (60 of them in the latest boot on one older Ivy Bridge laptop.) This has been reverted upstream and is not present in the next release. https://github.com/acpica/acpica/commit/df896f452f945d498736c5775d4ee6629df31786 (Also previously reverted in FreeBSD and Linux.)
2022-10-28drm(4): Mark PCI interrupt handlers as MP-safe.riastradh
2022-10-26ddb/db_active.h: New home for extern db_active.riastradh
This can be included unconditionally, and db_active can then be queried unconditionally; if DDB is not in the kernel, then db_active is a constant zero. Reduces need for #include opt_ddb.h, #ifdef DDB.
2022-10-25vmwgfx(4): Partially adapt rbtree.riastradh
2022-10-25linux asm/vmware.h: Fill this in with hypercall asm.riastradh
Not sure if it's necessary to support vmcall or vmmcall -- if so, need to deal with binary patching inline asm, ugh.
2022-10-25linux asm/uaccess.h: strncpy_from_userriastradh
(which does not actually have strncpy semantics, naturally, from what I can gather)
2022-10-25linux/frame.h: STACK_FRAME_NON_STANDARDriastradh
2022-10-25linux/kernel.h: S16_MIN, S32_MIN, S64_MINriastradh
2022-10-25linux/suspend.h: Stubs for (un)register_pm_notifier.riastradh
2022-10-25linux/pci.h: Stubs for pci_request/release_region(s).riastradh
2022-10-25linux/idr.h: Update ida_* API.riastradh
2022-10-25vmwgfx(4): Hand-cruft threaded irq with a workqueue(9).riastradh
2022-10-25drm: New IRQ_WAKE_THREAD constant.riastradh
Not really wired up to anything but helps reduce diffs -- driver is responsible for making decisions based on it, corresponding to Linux's built-in `threaded irq'.
2022-10-25vmwgfx(4): Port fd creation.riastradh
2022-10-25vmwgfx(4): Misc porting too.riastradh
- inl/outl -> bus_space_read/write - struct device for DMA stuff -> bus_dma_tag_t - spin_lock_destroy (and don't hold spin lock across kfree) - driver load/unload, fops, &c. - drm_irq_install/uninstall
2022-10-25vmwgfx(4): Use bus_dma tag, not struct device, for dma_pool shims.riastradh
2022-10-25vmwgfx(4): Convert fence_queue and fifo_queue to drm_waitqueue_t.riastradh
2022-10-25vmwgfx(4): Convert cmdbuf to drm_waitqueue_t.riastradh
2022-10-25linux/spinlock.h: spin_lock_bh, spin_unlock_bhriastradh
Nothing special needed here; NetBSD mutex(9) at IPL_* giving spin locks already blocks `BH' (i.e., softints -- although I'm not sure softints are relevant to the one use of this in vmwgfx).
2022-10-25linux asm/io.h: Side-load linux/vmalloc.h like Linux does.riastradh
2022-10-25linux/dmapool.h: Start filling out stubs.riastradh
2022-10-25vmwgfx(4): dma_alloc/free_coherent -> bus_dma_*riastradh
2022-10-25linux/module.h: MODULE_VERSIONriastradh
2022-10-25vmwgfx: Set some warning and config flags. Nix vmwgfx_fb.c for now.riastradh
2022-10-25linux/export.h: Side-load linux/stringify.h.riastradh
Expected by some users.
2022-10-17add pcie capability and read request size linux compat, some pci root supportmrg
implement support for: - pcie_capability_read_dword() - pcie_capability_read_word() - pcie_capability_write_dword() - pcie_capability_write_word() - pcie_get_readrq() - pcie_set_readrq() implement the "struct pci_dev" bus->self member by creating a minimal fake "struct pci_dev" for the pci bus itself. this is kind of gross. it checks that the current device's parent is a netbsd "pci" device, and that it has a (grand) parent "ppb" device, and then fills in the fake device based upon the pci and ppb devices. add some PCIE_LCSR2_TGT_LSPEED encodings, and map them to linux names. map several other PCIE_LCSR and PCIE_LCAP names. uncomment several pcie code segments in radeon and amdgpu. (not sure that we can test the amdgpu_si.c change, as we use the radeon version and the amdgpu version hangs on the one machine i have.) tested on amdgpu (RX550) and radeon (7750 & 3650). ok @riastradh
2022-10-15i915: Suspend ioctls while device is suspended.riastradh
2022-10-15drm: New mechanism to suspend ioctls during system suspend.riastradh
drm drivers must opt into this by calling drm_suspend_ioctl in their driver suspend routine, and drm_resume_ioctl in their driver resume routine. This is a stop-gap measure -- it would be better to fill in the pm_runtime_* API with new pmf(9) hooks to acquire/release references to devices for coordinating with suspend/resume, but getting the details right is tricky, and this stop-gap is enough to get i915 suspend/resume to work reliably on my Kaby Lake laptop. Rather than wait until I've got all the details right, let's just go with this stop-gap for now.
2022-10-08amdgpu: Remove an #ifdef __NetBSD__ around drm_waitqueue_t.riastradh
No functional change intended.