Zbigniew Bodek 76a8ef267d Avoid panic in ofwbus caused by not released resource list entry ... After resource allocation and release, resource list entry stays non-NULL. This causes panic in ofwbus_alloc_resource() on subsequent resource allocation. Clean appropriate list entry on release to avoid this. Obtained from: Semihalf Reviewed by: ian Sponsored by: The FreeBSD Foundation		2014-11-07 19:34:10 +00:00
..
ofw_bus_if.m	Move gpiobus routines to dev/gpio. Avoid polluting ofw_bus with bus	2014-05-04 04:01:26 +00:00
ofw_bus_subr.c	Replace multiple nearly-identical copies of code to walk through an FDT	2014-09-25 15:02:33 +00:00
ofw_bus_subr.h	Replace multiple nearly-identical copies of code to walk through an FDT	2014-09-25 15:02:33 +00:00
ofw_bus.h	Move gpiobus routines to dev/gpio. Avoid polluting ofw_bus with bus	2014-05-04 04:01:26 +00:00
ofw_console.c	Use callout(9) instead of timeout(9).	2014-09-02 18:57:19 +00:00
ofw_disk.c
ofw_fdt.c	Rename OF_xref_phandle() to OF_node_from_xref() and add a new function	2014-09-01 18:51:01 +00:00
ofw_if.m
ofw_iicbus.c	Allow the use of OFW I2C bus together with iicbb(4) on OFW-based systems.	2014-02-13 18:22:49 +00:00
ofw_pci.h
ofw_standard.c
ofwbus.c	Avoid panic in ofwbus caused by not released resource list entry	2014-11-07 19:34:10 +00:00
ofwvar.h
openfirm.c	When registering an association between a device and an xref phandle, create	2014-09-06 18:43:17 +00:00
openfirm.h	Revert rr271190, it was based on a misunderstanding. The problem of	2014-09-06 17:50:59 +00:00
openfirmio.c
openfirmio.h
openpromio.c
openpromio.h