Re: xf 4.0.1 with rage II/rage pro -- multi-headed display!

quoted

I've posted such a patch to debian-powerpc when one user there had this
problem. That was before I learned booting with yaboot avoids the problem.
If the resource conflict also happens on oldworld machines, I'd still
prefer some suggestions to foolproof the patch (as in: how can I figure
out if a region has been allocated by another card? What bits from the
config registers should I look at?).

You should walk all PCI devices and construct your own resource tree from
pci_dev->base_address[i]. After that you know the conflicts and unassigned
addresses and can look for free space. Unfortunately this is probably nearly
as much work as backporting the 2.4.x PCI resource code (which is tested,
unlike new code you would invent).

Yep, I'm aware of that. I'm way too lazy to backport the PCI resource code
and the problem seemed solved by using yaboot for me. I didn't
fully realize the Wallstreet doesn't have this option.

Instead of walking the whole device tree, I hope to get away with just
picking a free area (assuming pci_dev->base_address[i] == 0 means free)
instead. But I won't get to it before the weekend. If BenH implements a
cleaner way, the better.

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/