Marius Strobl 42be1191a0 - When iterating over the register resources of the children don't use ... the iteration variable as the RID when adding the respective resource to the child via bus_set_resource(). In case a device has both I/O and memory resources this generates gaps in the newbus resources of the child, e.g. its first memory resource might end up as RID 1. To solve this mimic resource_list_add_next() via resource_list_find() and bus_set_resource(); we can't just use resource_list_add_next() here as this would circumvent the limit checks in isa_set_resource() of the common ISA code. This however is more or less a theoretical problem so far as all known ISA devices on sparc64 soley use I/O space. - Just use bus_generic_rl_release_resource() for isa_release_resource() instead of re-implementing the former. - Improve some comments to better reflect reality, minor clean-up and simplifications, return NULL instead of 0 were appropriate.		2005-05-19 15:47:37 +00:00
..
isa_dma.c	Since we are quite unlikely to ever face another platform which	2005-02-06 13:46:39 +00:00
isa.c	- When iterating over the register resources of the children don't use	2005-05-19 15:47:37 +00:00
ofw_isa.c
ofw_isa.h