From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Feng Kan <fkan@amcc.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: RE: Broken PCI on Sequoia
Date: Sat, 31 Jan 2009 15:42:33 +1100 [thread overview]
Message-ID: <1233376953.18767.40.camel@pasglop> (raw)
In-Reply-To: <2B3B2AA816369A4E87D7BE63EC9D2F260674E7E3@SDCEXCHANGE01.ad.amcc.com>
On Fri, 2009-01-30 at 17:19 -0800, Feng Kan wrote:
> Hi:
> It looks like the top bit is hard coded to 1. There doesn't seem to
> be anyway
> Of changing it.
Thanks !
Would it be possible for you to check other 4xx parts using that PCI
controller as to whether the top bit is always hard-coded to 1 or it
changes from part to part ?
Thanks !
Cheers,
Ben.
> Feng Kan
> AMCC Engineering
>
> -----Original Message-----
> From: linuxppc-dev-bounces+fkan=amcc.com@ozlabs.org
> [mailto:linuxppc-dev-bounces+fkan=amcc.com@ozlabs.org] On Behalf Of
> Benjamin Herrenschmidt
> Sent: Friday, January 30, 2009 1:30 PM
> To: Geert Uytterhoeven
> Cc: Linux/PPC Development
> Subject: Re: Broken PCI on Sequoia
>
>
> > For that sort of 4xx PHB (ie, the PCI 2.x ones, not the PCI-X nor the
> > PCI-E), we only know how to program 32-bit of PLB address. IE. The old
> > code would have cropped the plb_addr when writing to the register, the
> > new code complains.
> >
> > I suspect some implementation support a register to put the "high"
> part
> > of the PLB address, and that it already contains 1, so the old code
> > would have worked by chance, the new code doesn't because it bails
> out.
>
> Hrm... from the doco it's also one 32-bit register... I'm starting to
> think that those guys always assume the top 1 bit is set or something
> like that ...
>
> The doc is unclear. Maybe somebody form AMCC can confirm ?
>
> Cheers,
> Ben.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
prev parent reply other threads:[~2009-01-31 4:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 17:37 Broken PCI on Sequoia Geert Uytterhoeven
2009-01-29 22:11 ` Benjamin Herrenschmidt
2009-01-30 0:18 ` Josh Boyer
2009-01-30 2:08 ` Benjamin Herrenschmidt
2009-01-30 12:35 ` Geert Uytterhoeven
2009-01-30 21:02 ` Benjamin Herrenschmidt
2009-01-30 21:30 ` Benjamin Herrenschmidt
2009-01-31 1:19 ` Feng Kan
2009-01-31 4:42 ` Benjamin Herrenschmidt [this message]
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=1233376953.18767.40.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=fkan@amcc.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).