Marius Strobl 606de9ed4d At least on some U30 there's a spurious duplicate device node of an EBus ... bridge in the device tree which lacks the mandatory (also by the OFW PCI bus binding spec) "reg" property. Change the code to just ignore nodes missing the "reg" property instead of panicing when encountering such a node. Also ignore nodes without a "name" property (guaranteed by the OFW PCI bus binding spec). This brings the behaviour of the MD OFW PCI code regarding such incomplete nodes in line with the EBus and the SBus code. Tested by: Cyril Tikhomiroff <tikho@anor.net> MFC after: 1 month		2005-01-20 13:29:31 +00:00
..
central	- Introduce an ofw_bus kobj-interface for retrieving the OFW node and a	2004-08-12 17:41:33 +00:00
compile
conf	Fixed sparc64 LINT build.	2005-01-14 13:16:13 +00:00
creator	- Add missing <sys/module.h>. [1]	2004-07-09 23:12:22 +00:00
ebus	Don't panic when we're asked to allocate a resource type that we know	2005-01-09 18:58:08 +00:00
fhc	- Introduce an ofw_bus kobj-interface for retrieving the OFW node and a	2004-08-12 17:41:33 +00:00
include	Add a small API to manage the MD user trap structures. Specifically, we	2005-01-19 18:24:07 +00:00
isa	/* -> /*- for license, minor formatting changes	2005-01-07 02:29:27 +00:00
pci	At least on some U30 there's a spurious duplicate device node of an EBus	2005-01-20 13:29:31 +00:00
sbus	/* -> /*- for license, minor formatting changes	2005-01-07 02:29:27 +00:00
sparc64	Add a small API to manage the MD user trap structures. Specifically, we	2005-01-19 18:24:07 +00:00