History log of /freebsd/sys/dev/ofw/ofw_firmware.c (Results 1 – 4 of 4)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 18250ec6 06-Dec-2024 John Baldwin <jhb@FreeBSD.org>

Replace calls to bus_generic_attach with bus_attach_children

Reviewed by: imp
Differential Revision: https://reviews.freebsd.org/D47675


Revision tags: release/14.2.0, release/13.4.0, release/14.1.0, release/13.3.0, release/14.0.0
# 81b41b2e 15-Aug-2023 Emmanuel Vadot <manu@FreeBSD.org>

ofw_firmware: Return BUS_PROBE_GENERIC instead of 0

While here make it only probe if the node is directly under the root
one. If it's not it's likely a device node named 'firmware' and not the
firmw

ofw_firmware: Return BUS_PROBE_GENERIC instead of 0

While here make it only probe if the node is directly under the root
one. If it's not it's likely a device node named 'firmware' and not the
firmware group we're interested in.

Suggested by: jhb
Sponsored by: Beckhoff Automation GmbH & Co. KG

show more ...


# 69f8cc60 13-Aug-2023 Emmanuel Vadot <manu@FreeBSD.org>

ofw_firmware: Only match if there is no compatible

If there is a compatible string it likely means that the firmware needs
a dedicated driver (like on RPI*).

PR: 273087
Tested-by: Mark Millard <mar

ofw_firmware: Only match if there is no compatible

If there is a compatible string it likely means that the firmware needs
a dedicated driver (like on RPI*).

PR: 273087
Tested-by: Mark Millard <marklmi26-fbsd@yahoo.com>
Sponsored by: Beckhoff Automation GmbH & Co. KG
Fixes: fdfd3a90b6ce ("ofw: Add a ofw_firmware driver")

show more ...


Revision tags: release/13.2.0
# fdfd3a90 06-Dec-2022 Emmanuel Vadot <manu@FreeBSD.org>

ofw: Add a ofw_firmware driver

Some SoCs have an external firmware doing power management, clock
and other stuffs. (Xilinx, ARM Juno etc ...)
The way it is represent in the DTB is usually having a '

ofw: Add a ofw_firmware driver

Some SoCs have an external firmware doing power management, clock
and other stuffs. (Xilinx, ARM Juno etc ...)
The way it is represent in the DTB is usually having a 'firmware' node
under the root node and have some nodes under it with the correct
compatible strings.
The firmware node itself doesn't have any compatible strings.
This driver is simple subclassed from simplebus and attaches at
BUS_PASS_BUS + BUS_PASS_ORDER_MIDDLE so early drivers (like clock drivers)
can still have a change to attach early.

Reviewed by: andrew
Sponsored by: Beckhoff Automation GmbH & Co. KG
Differential Revision: https://reviews.freebsd.org/D37612

show more ...