From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org, Patrick Mochel <mochel@osdl.org>
Subject: Re: [patch 2.5.31] transparent PCI-to-PCI bridges
Date: Sun, 1 Sep 2002 02:40:19 +0400 [thread overview]
Message-ID: <20020901024019.A2888@jurassic.park.msu.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0208310940510.2129-100000@home.transmeta.com>; from torvalds@transmeta.com on Sat, Aug 31, 2002 at 09:49:14AM -0700
On Sat, Aug 31, 2002 at 09:49:14AM -0700, Linus Torvalds wrote:
>
> On 31 Aug 2002, Alan Cox wrote:
> >
> > Related question while we are on the subject of bridges. I'm trying to
> > work out a clean way to initialize a new subtree of devices given a
> > bridge that suddenely has devices behind it.
> >
> > This occurs in three cases I know about now
> > - Easidock cardbus->PCI extender
> > - IBM Thinkpad hot docking bridge
> > - Magma PCI extended split bridge
>
> pci_do_scan_bus() should do almost everything for you. Pat Mochel had some
> code that made the cardbus driver basically do just this on cardbus
> insertion, you might ask him.
I guess Pat's code has something to do with a resource allocation
(haven't seen it though).
I would play with following if I have the hardware:
{
pci_do_scan_bus(bus);
pbus_size_bridges(bus);
pbus_assign_resources(bus);
}
Obviously, __init qualifiers should be changed to __devinit for pbus_*
and other stuff in setup-bus.c and setup-res.c.
Ivan.
next prev parent reply other threads:[~2002-08-31 22:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-25 16:55 [patch 2.5.31] transparent PCI-to-PCI bridges Manfred Spraul
2002-08-26 13:57 ` Ivan Kokshaysky
2002-08-26 17:42 ` Linus Torvalds
2002-08-28 0:58 ` Ivan Kokshaysky
2002-08-28 1:29 ` Linus Torvalds
2002-08-30 21:38 ` [patch 2.5.32] " Ivan Kokshaysky
2002-08-26 20:12 ` [patch 2.5.31] " Benjamin Herrenschmidt
2002-08-28 1:40 ` Ivan Kokshaysky
2002-08-28 10:03 ` Benjamin Herrenschmidt
2002-08-28 17:35 ` Linus Torvalds
2002-08-28 18:35 ` Benjamin Herrenschmidt
2002-08-29 23:53 ` Ivan Kokshaysky
2002-08-30 9:28 ` Benjamin Herrenschmidt
2002-08-30 21:57 ` Ivan Kokshaysky
2002-08-30 20:19 ` Benjamin Herrenschmidt
2002-08-31 10:42 ` Ivan Kokshaysky
2002-08-31 15:06 ` Alan Cox
2002-08-31 16:49 ` Linus Torvalds
2002-08-31 22:40 ` Ivan Kokshaysky [this message]
2002-08-31 8:09 ` Benjamin Herrenschmidt
2002-08-30 17:12 ` Linus Torvalds
2002-08-30 22:23 ` Ivan Kokshaysky
2002-08-31 8:09 ` Benjamin Herrenschmidt
2002-08-31 13:12 ` Ivan Kokshaysky
2002-08-31 16:29 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2002-08-24 20:17 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=20020901024019.A2888@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.com \
/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