FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F13.2.0 2022-08-22T09:11:29Z 2022-08-22T09:11:29Z Andrew Turner andrew@FreeBSD.org 2022-08-11T12:02:50Z urn:sha1:36e31c79cea1684198706b9222ebe78346f39b2b With clang 15, the following -Werror warning is produced: sys/dev/ofw/openfirm.c:826:9: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes] OF_enter() ^ void This is because OF_enter() and OF_exit are declared with a (void) argument list, but defined with an empty argument list. Make the definition match the declaration. Sponsored by: The FreeBSD Foundation (cherry picked from commit ec666d187d0dc44d105a95b5b25b47607236a051) 2022-05-16T11:45:38Z Emmanuel Vadot manu@FreeBSD.org 2022-01-11T10:08:18Z urn:sha1:8d672e8449c877b2772d5f7b0a3dc1b7123ad226 EXT_RESOURCES have been introduced in 12-CURRENT and all supported releases have it enabled in their kernel config. For RISC-V it was always enabled. MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D33835 (cherry picked from commit 02398e581d4511bd1c5e8ffad5155f9b9684b4b8) 2022-03-09T15:28:28Z Mike Karels karels@FreeBSD.org 2022-02-23T20:42:30Z urn:sha1:c0d9004101dbd9637a6b7e1b876f8eece489a5cf Add serial-number sysctl if that fdt property exists and is a printable string. While here, ensure that the hw.fdt sysctl values fit in the buffers provided so that they will be NUL-terminated. Tested on Raspberry Pi 3B+ and 4. Reviewed by: manu imp Differential Revision: https://reviews.freebsd.org/D34356 (cherry picked from commit b8b0c65e8a43cab95b97e28d3e3d73fc7d9c0a5e) 2022-03-09T15:27:28Z Emmanuel Vadot manu@FreeBSD.org 2021-07-17T15:19:22Z urn:sha1:caa14c7b600d3d15042ada340665f7b0aed4b415 This make it easier for script to get the hardware on which they are running. Sponsored by: Diablotin Systems Differential Revision: https://reviews.freebsd.org/D31205 Reviewed by: imp Should be ok on powerpc: jhibbits (over irc) (cherry picked from commit 50e0dc0c4b46ee62b898ce2d92e52be4f77383d9) 2022-02-08T20:00:55Z Ed Maste emaste@FreeBSD.org 2021-08-08T14:38:01Z urn:sha1:94e6d1448863a8ccccec3c7e4e501761803cce0e These ones were unambiguous cases where the Foundation was the only listed copyright holder (in the associated license block). Sponsored by: The FreeBSD Foundation (cherry picked from commit 9feff969a01044c3083b552f06f7eb6416bc0524) 2022-01-20T10:00:55Z Michal Meloun mmel@FreeBSD.org 2021-06-24T09:56:20Z urn:sha1:57dd17dd60e7bb618ab2979df2d580559fcf3729 By definition ofw_bus_get_node() should consistently return -1 when there is no associated OF node. MFC after: 4 weeks Discussed with: nwhitehorn Analyzed in: https://reviews.freebsd.org/D30761 (cherry picked from commit 3eae4e106ac7222364fc9dc8c3d35d4ad8c5293a) 2021-06-14T20:25:14Z Mark Johnston markj@FreeBSD.org 2021-06-06T20:40:19Z urn:sha1:5346c8bc543a09932b168f459e8a7a601af4bfdc During boot we warn that the kbd and openfirm drivers are Giant-locked and may be deleted. Generally, the warning helps signal that certain old drivers are not being maintained and are subject to removal, but this doesn't really apply to certain drivers which are harder to detangle from Giant. Add a flag, D_GIANTOK, that devices can specify to suppress the misleading warning. Use it in the kbd and openfirm drivers. Reviewed by: imp, jhb Sponsored by: The FreeBSD Foundation (cherry picked from commit fbeb4ccac990fdb3bc26ab925a3ca8e7d2f89721) 2021-01-16T22:53:13Z Marius Strobl marius@FreeBSD.org 2021-01-16T11:49:47Z urn:sha1:daad26e5fc256767d6b97f07a519e765f1664f69 It's unused since 58aa35d42975c298ca0adba705c042596303c9f5 and r357455 respectively and should have gone along with these. 2020-11-13T16:49:41Z Brandon Bergren bdragon@FreeBSD.org 2020-11-13T16:49:41Z urn:sha1:26869ad14c70306313405029229a1e2fd94510cd In standards such as LoPAPR, property names in excess of the usual 31 characters exist. This breaks property traversal. While in IEEE 1275-1994, nextprop is defined explicitly to work with a 32-byte region of memory, using a larger buffer should be fine. There is actually no way to pass a buffer length to the nextprop call in the OF client interface, so SLOF actually just blindly overflows the buffer. So we have to defensively make the buffer larger, to avoid memory corruption when reading out long properties on live OF systems. Note also that on real-mode OF, things are pretty tight because we are allocating against a static bounce buffer in low memory, so we can't just use a huge buffer to work around this without it being wasteful of our limited amount of 32-bit physical memory. This allows a patched ofwdump to operate properly on SLOF (i.e. pseries) systems, as well as any other PowerPC systems with overlength properties. Reviewed by: jhibbits MFC after: 2 weeks Sponsored by: Tag1 Consulting, Inc. Differential Revision: https://reviews.freebsd.org/D26669 2020-09-01T22:01:53Z Mateusz Guzik mjg@FreeBSD.org 2020-09-01T22:01:53Z urn:sha1:f9874fbbf177e0284f8c65c050a51b40e35be4de