PCI resource initialisation

David Monro davidm at amberdata.demon.co.uk
Sun Aug 27 07:20:54 EST 2000


I need to make some changes to the way we do our PCI resource allocation

Currently the code goes like this (in pci.c:pcibios_init()):

        pci_scan_bus(0, &generic_pci_ops, NULL);
        if (ppc_md.pcibios_fixup)

So we find all the devices, hack any we don't like, and then grab all
the resources. This means that we pretty much accept whatever the
firmware provides, which includes leaving any uninitialised resources
alone. This doesn't work properly on IBM 850 machines because the
firmware doesn't initialise any devices it doesn't recognise, and also
(for example) doesn't bother initialising the memory mapped resource of
the built-in ethernet (presumably because they expected people to use
the IO resource instead, which in fact we do).

The 2.4 kernel does provide a function,
pci_assign_unassigned_resources(), which will find pci resources which
haven't been claimed yet and do the appropriate thing with them.

As I see it we have a few choices:

	pci_scan_bus(0, &generic_pci_ops, NULL);
        if (ppc_md.pcibios_fixup)

which should allocate any left alone by the original code, and does
work, but still means we have to hack the original resources (eg on IBM
850s the SCSI hos adapters seem to always get allocated IO port
resources above 0x20000000, which we relocate in a not very safe manner
down to 0x01000000). It also assumes we don't need to do any more fixups
for the newly discovered resources.

or we could do:
	pci_scan_bus(0, &generic_pci_ops, NULL);
        if (ppc_md.pcibios_fixup)

which results in the kernel completely reassigning all the PCI
resources. This should mean that the resources all get allocated in
areas that we would like to find them in, and means that the
pcibios_fixup code should be a little simpler. This is my preferred
solution, but I guess might break something.

Note that I can't really do this just for the PReP code; if I put the
pci_assign_unassigned_resources() call in the prep_pcibios_fixup()
function it will completely remap the bus and claim all the resources,
and then pcibios_claim_resources() will walk the tree trying to claim
each resource again and get a conflict on every resource!

Of course we could simply make pcibios_init() another arch-dependant
function - what do people think?

On a related, is it true to say that every driver which uses ioremap()
to map memory on cards into virtual space needs to have isa_mem_base
added to the base address before it will work? As far as I can tell
virtually no drivers do this at the moment; I note a rather
dirty-looking hack in chrp_pci.c where we hack the resource entries for
the matrox card so that the driver doesn't need rewriting. Or should we
simply do this for all memory resources on all cards?



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

More information about the Linuxppc-dev mailing list