src/sys/dev/agp, branch releng/14.2FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F14.22024-09-05T13:44:03Zagp: Set the driver-specific field correctly2024-09-05T13:44:03ZMark Johnstonmarkj@FreeBSD.org2024-08-29T13:12:19Zurn:sha1:57e0d4b9a609cc2fe267489a3fe46857035ed3ae
PR: 281035
Reviewed by: mhorne
MFC after: 1 week
Fixes: 437ea82ce7fc ("agp: Handle multiple devices more gracefully")
(cherry picked from commit 12500c14281dc62ddeac4c5e1e6eabd1e380f11c)
pci_cfgreg: Add a PCI domain argument to the low-level register API2024-01-18T22:44:51ZJohn Baldwinjhb@FreeBSD.org2023-11-29T18:31:47Zurn:sha1:98b822fccd8350f59eb2deb842c52c35b145c2cb
This commit changes the API of pci_cfgreg(read|write) to add a domain
argument (referred to as a segment in ACPI parlance) (note that this
is not the same as a NUMA domain, but something PCI-specific). This
does not yet enable access to domains other than 0, but updates the
API to support domains.
Places that use hard-coded bus/slot/function addresses have been
updated to hardcode a domain of 0. A few places that have the PCI
domain (segment) available such as the acpi_pcib_acpi.c Host-PCI
bridge driver pass the PCI domain.
The hpt27xx(4) and hptnr(4) drivers fail to attach to a device not on
domain 0 since they provide APIs to their binary blobs that only
permit bus/slot/function addressing.
The x86 non-ACPI PCI bus drivers all hardcode a domain of 0 as they do
not support multiple domains.
Reviewed by: imp
Differential Revision: https://reviews.freebsd.org/D42827
(cherry picked from commit 1587a9db92c03c738bb3f0fc5874b43c961e7c99)
agp_amd64: Use <machine/pci_cfgreg.h> rather than bare prototypes2024-01-04T23:13:26ZJohn Baldwinjhb@FreeBSD.org2023-11-29T18:31:16Zurn:sha1:1309b3fd01138c7a65a22c2297f261be3d313f0e
Reviewed by: imp
Differential Revision: https://reviews.freebsd.org/D42826
(cherry picked from commit 71ac18a84df2771fb9bd91e2349eae91602c4e46)
sys: Remove $FreeBSD$: one-line sh pattern2023-08-16T17:54:58ZWarner Loshimp@FreeBSD.org2023-08-16T17:54:58Zurn:sha1:031beb4e239bfce798af17f5fe8dba8bcaf13d99
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
sys: Remove $FreeBSD$: one-line .c pattern2023-08-16T17:54:36ZWarner Loshimp@FreeBSD.org2023-08-16T17:54:36Zurn:sha1:685dc743dc3b5645e34836464128e1c0558b404b
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
sys: Remove $FreeBSD$: two-line .h pattern2023-08-16T17:54:11ZWarner Loshimp@FreeBSD.org2023-08-16T17:54:11Zurn:sha1:95ee2897e98f5d444f26ed2334cc7c439f9c16c6
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD2023-05-12T16:44:03ZWarner Loshimp@FreeBSD.org2023-05-10T15:40:58Zurn:sha1:4d846d260e2b9a3d4d0a701462568268cbfe7a5b
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
kmem_malloc/free: Use void * instead of vm_offset_t for kernel pointers.2022-09-22T22:09:19ZJohn Baldwinjhb@FreeBSD.org2022-09-22T22:09:19Zurn:sha1:f49fd63a6a130ae464cdc7756e6f7d0d747c82c4
Reviewed by: kib, markj
Sponsored by: DARPA
Differential Revision: https://reviews.freebsd.org/D36549
Adjust agp_find_device() definition in agp.c to avoid clang 15 warning2022-07-16T14:46:21ZDimitry Andricdim@FreeBSD.org2022-07-16T14:46:21Zurn:sha1:c0817e2aba26ceb683e9c649c22d7fcd9a921231
With clang 15, the following -Werror warning is produced:
sys/dev/agp/agp.c:910:16: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
agp_find_device()
^
void
This is because agp_find_device() is declared with a (void) argument
list, and defined with an empty argument list. Make the definition match
the declaration.
MFC after: 3 days
vm_object: Modify various drivers to allocate OBJT_SWAP objects2022-07-12T13:10:15ZMark Johnstonmarkj@FreeBSD.org2022-07-12T12:51:02Zurn:sha1:6b38974085215bcd787be0d138411ec57cf0096e
This is in preparation for removal of OBJT_DEFAULT. In particular, it
is now cheap to check whether an OBJT_SWAP object has any swap blocks
allocated, so the benefit of having a separate OBJT_DEFAULT type is
quite marginal, and the OBJT_DEFAULT->SWAP transition is a source of
bugs.
Reviewed by: alc, hselasky, kib
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D35779