From: Benjamin Herrenschmidt <bh40@calva.net>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
<linux-kernel@vger.kernel.org>
Subject: Re: PCI bridge setup weirdness
Date: Fri, 8 Dec 2000 15:31:08 +0100 [thread overview]
Message-ID: <19341102080252.6877@192.168.1.2> (raw)
In-Reply-To: <20001208155128.A2926@jurassic.park.msu.ru>
In-Reply-To: <20001208155128.A2926@jurassic.park.msu.ru>
>
>No, pci_read_bridge_bases() is obsoleted by new pci setup code. ;-)
>You have to set up bus resources properly in pcibios_fixup_bus().
>For a single root bus configuration, you don't need to do anything
>with the root bus itself - its resources already point to ioport_resource
>and iomem_resource, which should be ok. For pci-pci bridges you have
>to add something like this:
The problem I have (and this is why I don't setup host resources
properly on multi-host PPCs yet) is that some hosts can have several
non-contiguous ranges (especially with memory, IO is usually a single
contiguous range).
There are simply not enough resource "slots" in the current structures
to handle all possibles cases.
They basically have a host bridge register in which each low bit enables
decoding of a 256Mb region in the range 0xn0000000 and each high bit
enable decoding of a 16Mb region in the range 0xFn000000
The typical setup is to have one (or more) 256Mb regions, and one 16Mb
region, but that can change from model to model.
Ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 22:46 PCI bridge setup weirdness Russell King
2000-12-08 12:51 ` Ivan Kokshaysky
2000-12-08 14:31 ` Benjamin Herrenschmidt [this message]
2000-12-09 10:49 ` Ivan Kokshaysky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19341102080252.6877@192.168.1.2 \
--to=bh40@calva.net \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox