> Like recently added `drq2', should we have `port2'?

Doesn't help a lot. I'm just dealing with cards that have:
 - one config port range
 - one general port range
 - three ranges for three major chips on the card

all of this scatered through io-space. Luckily they have constant
offsets from each other, so I only need one value (the user selectable).

Allowing arbitrary numbers of (bus_space_tag_t space, bus_size_t offset)
tuples would be the right way to go...


Martin