From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Felix Radensky <felix@embedded-sol.com>
Cc: Stef van Os <stef.van.os@Prodrive.nl>, Stefan Roese <sr@denx.de>,
Feng Kan <fkan@amcc.com>,
linuxppc-dev@ozlabs.org
Subject: Re: PCI-PCI bridge scanning broken on 460EX
Date: Tue, 12 Jan 2010 09:53:34 +1100 [thread overview]
Message-ID: <1263250414.724.161.camel@pasglop> (raw)
In-Reply-To: <4B4BAAC0.4010300@embedded-sol.com>
On Tue, 2010-01-12 at 00:48 +0200, Felix Radensky wrote:
>
> Maybe because the bus behind root P2P bridge is bus 0, and type 1
> cycles are
> needed for bus numbers greater than 0. That's what 460EX manual says.
Well, no... the bus behind the root P2P is bus 1 ... the root P2P itself
is on bus 0... but then, it's some trick in the way they implemented it
I suppose.
> You are correct, the log is from older version, without Stef's fix. I
> don't have access to a
> system with devices behind PLX, and the guy who did the testing used
> wrong kernel.
> I'll make sure he uses the correct one and get back to you. Maybe
> everything works after all :)
> I'm really sorry for confusion.
No worries :-) Feel free to send a proper patch to fix that problem
upstream too !
Cheers,
Ben.
next prev parent reply other threads:[~2010-01-11 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 10:51 PCI-PCI bridge scanning broken on 460EX Felix Radensky
2010-01-04 5:55 ` Benjamin Herrenschmidt
2010-01-04 8:59 ` Felix Radensky
2010-01-10 12:56 ` Felix Radensky
2010-01-10 20:38 ` Benjamin Herrenschmidt
2010-01-10 21:13 ` Felix Radensky
2010-01-10 21:31 ` Benjamin Herrenschmidt
2010-01-11 9:58 ` Stef van Os
2010-01-11 11:48 ` Felix Radensky
2010-01-11 16:46 ` Felix Radensky
2010-01-11 20:53 ` Benjamin Herrenschmidt
2010-01-11 22:48 ` Felix Radensky
2010-01-11 22:53 ` Benjamin Herrenschmidt [this message]
2010-01-12 11:02 ` Felix Radensky
2010-01-12 11:14 ` Stef van Os
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=1263250414.724.161.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=felix@embedded-sol.com \
--cc=fkan@amcc.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
--cc=stef.van.os@Prodrive.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.