From: "Russell McGuire" <rmcguire@videopresence.com>
To: "'Kumar Gala'" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: 8360E - PCI / DTC Blob Setup
Date: Fri, 2 Feb 2007 21:32:44 -0800 [thread overview]
Message-ID: <000701c74754$bbd23910$6405a8c0@absolut> (raw)
In-Reply-To: <CBE9C97B-2A34-4D56-B7E8-F46728EF29F6@kernel.crashing.org>
> On Feb 2, 2007, at 7:36 AM, Russell McGuire wrote:
>
> >
> > Well I am getting smarter on this:
> >
> > I have read through the PCI Bridge Specs and found another issue
> > that might
> > have been causing a problem with the IDSEL lines. Unless you are
> > interested
> > I'll forgo that explanation and just go with fact that I have
> > changed the
> > IDSEL mappings to be legal when they are issued from the 83xx.
> >
> > I have changed the IDSELs to be as follows, does this look correct?
>
> Not sure, I'm a little confused as to how exactly things are wired on
> your board. It would seem like you have 2 P2P bridges connected to
> the processor. Behind one bridge is 2 slots and behind the second is
> 1 slot?
Absolutely correct, I probably should send a picture. :-) But yes, the CPU
host bridge is directly connected to a DUAL P2P bridge chip. There are no
SLOTS on BUS 0. The P2P then provides BUS 1 and BUS 2. I did this in the
design to allow slower 33Mhz cards to operate in the system without slowing
down the 66Mhz cards <i.e. a sound card or USB card, but still being able to
run a VGA card or video capture card at high speed>.
BUS 1 has two slots, and BUS 2 has one slot, for a total of three.
I would be more than happy to send a 2 page PDF file of the schematic. This
design obviously hasn't been proofed yet. Though it 'seems' to almost work.
-Russ
next prev parent reply other threads:[~2007-02-03 5:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1454.1170226011.9285.linuxppc-embedded@ozlabs.org>
2007-01-31 12:14 ` Audigy SE / ca0106 driver for PowerPC? Russell McGuire
2007-01-31 14:52 ` Kumar Gala
2007-01-31 15:20 ` Russell McGuire
2007-01-31 15:34 ` Kumar Gala
2007-01-31 21:00 ` Russell McGuire
2007-01-31 21:55 ` Kumar Gala
2007-01-31 22:27 ` Russell McGuire
2007-01-31 22:40 ` Kumar Gala
2007-01-31 23:01 ` Russell McGuire
2007-01-31 23:19 ` Kumar Gala
2007-01-31 23:42 ` Russell McGuire
2007-01-31 23:49 ` Kumar Gala
2007-02-01 14:27 ` 8360E - PCI / DTC Blob Setup Russell McGuire
2007-02-01 14:33 ` Kumar Gala
2007-02-01 17:48 ` Russell McGuire
2007-02-01 18:11 ` Kumar Gala
2007-02-02 2:49 ` Russell McGuire
2007-02-02 6:20 ` Kumar Gala
2007-02-02 13:36 ` Russell McGuire
2007-02-02 15:48 ` Kumar Gala
2007-02-03 5:32 ` Russell McGuire [this message]
2007-02-05 1:45 ` Benjamin Herrenschmidt
2007-02-08 3:07 ` Andy Fleming
[not found] ` <000501c74592$2229e060$6405a8c0@absolut>
[not found] ` <53119C53-A3A7-4808-849A-09226BBEAC3B@kernel.crashing.org>
2007-02-01 9:00 ` Audigy SE / ca0106 driver for PowerPC? Russell McGuire
2007-02-01 14:22 ` Kumar Gala
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='000701c74754$bbd23910$6405a8c0@absolut' \
--to=rmcguire@videopresence.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@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).