sys/dev: further adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - error
sys/dev: further adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - errorprone - task.The Software Package Data Exchange (SPDX) group provides a specificationto make it easier for automated tools to detect and summarize well knownopensource licenses. We are gradually adopting the specification, notingthat the tags are considered only advisory and do not, in any way,superceed or replace the license texts.
show more ...
Consistently use `device_t`Several files use the internal name of `struct device` instead of`device_t` which is part of the public API. This patch changes all`struct device *` to `device_t`.The
Consistently use `device_t`Several files use the internal name of `struct device` instead of`device_t` which is part of the public API. This patch changes all`struct device *` to `device_t`.The remaining occurrences of `struct device` are those referring to theLinux or OpenBSD version of the structure, or the code is not built onFreeBSD and it's unclear what to do.Submitted by: Matthew Macy <[email protected]> (previous version)Approved by: emaste, jhibbits, sbrunoMFC after: 3 daysDifferential Revision: https://reviews.freebsd.org/D7447
Use DEVMETHOD_END macro defined in sys/bus.h instead of {0, 0} sentinel on device_method_t arraysReviewed by: cognetApproved by: cognet
Enroll these drivers in multipass probing. The motivation behind thisis that the JBus to EBus bridges share the interrupt controller of asibling JBus to PCIe bridge (at least as far as the OFW devi
Enroll these drivers in multipass probing. The motivation behind thisis that the JBus to EBus bridges share the interrupt controller of asibling JBus to PCIe bridge (at least as far as the OFW device treeis concerned, in reality they are part of the same chip) so we have toprobe and attach the latter first. That happens to be also the casedue to the fact that the JBus to PCIe bridges appear first in the OFWdevice tree but it doesn't hurt to ensure the right order.
Provide and consume missing module dependency information.
- Only touch the LED bit of the (LED) AUXIO register when turning the system LED on or off. Unlike the EBus LED AUXIO register where the remaining bits are unused the upper bits of the SBus AUXIO
- Only touch the LED bit of the (LED) AUXIO register when turning the system LED on or off. Unlike the EBus LED AUXIO register where the remaining bits are unused the upper bits of the SBus AUXIO register are used to control other things like the link test enable pin of the on-board NIC which we don't want to change as a side-effect.- Remove the superfluous bzero()'ing of the softc obtained from device_get_softc().Reviewed by: yongariMFC after: 3 days
Switch from trying to allocate up to 8 register banks for the EBusvariant to allocating a fixed set of 5 banks that the EBus variantis documented to have (and also has in reality). Trying to alloca
Switch from trying to allocate up to 8 register banks for the EBusvariant to allocating a fixed set of 5 banks that the EBus variantis documented to have (and also has in reality). Trying to allocateup to 8 banks is a remnant from experiments during the developmentof this driver.Discussed with: joerg, yongariReviewed by: yongariApproved by: re (scottl)
- Take advantage of ebus(4) having switched to SYS_RES_MEMORY for memory resources in ebus.c rev. 1.22 and collapse the resource allocation for both the EBus and SBus variants into auxio_attach_c
- Take advantage of ebus(4) having switched to SYS_RES_MEMORY for memory resources in ebus.c rev. 1.22 and collapse the resource allocation for both the EBus and SBus variants into auxio_attach_common().- For the EBus variant make sure that the resource for controlling the LED is actually available; (in theory) we could have ended up using the resource without allocating it.
Start each of the license/copyright comments with /*-, minor shuffle of lines
Port NetBSD auxio driver. The driver was modified to use led(4) and canbe used to announce various system activity.The auxio device provides auxiliary I/O functions and is found on variousSBus/EBu
Port NetBSD auxio driver. The driver was modified to use led(4) and canbe used to announce various system activity.The auxio device provides auxiliary I/O functions and is found on variousSBus/EBus UltraSPARC models. At present, only front panel LED iscontrolled by this driver.Approved by: jake (mentor)Reviewed by: joergTested by: joerg