From: Todd Poynor <tpoynor@mvista.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: very minor 405GP and 405GPr PCI difference
Date: Fri, 04 Oct 2002 11:33:13 -0700 [thread overview]
Message-ID: <3D9DDEE9.5070909@mvista.com> (raw)
In-Reply-To: 20021004024832.GG1933@zax
David Gibson wrote:
> + /* Now configure the PCI->PLB windows, we only use PTM1 */
> + out_le32((void *) &(pcip->ptm1ms), 0x00000000); /* first disable */
> + out_le32((void *) &(pcip->ptm1la), 0x00000000); /* base address */
> + out_le32((void *) &(pcip->ptm1ms), 0x80000001); /* re-enable */
> + out_le32((void *) &(pcip->ptm2ms), 0x00000000); /* disable PTM2 */
> +
> + /* Zero config bars */
> + for (bar = PCI_BASE_ADDRESS_1; bar <= PCI_BASE_ADDRESS_2; bar += 4) {
> + early_write_config_dword(hose, hose->first_busno,
> + PCI_FUNC(hose->first_busno), bar,
> + 0x00000000);
> + early_read_config_dword(hose, hose->first_busno,
> + PCI_FUNC(hose->first_busno), bar,
> + &bar_response);
> + DBG("BUS %d, device %d, Function %d bar 0x%8.8x is 0x%8.8x\n",
> + hose->first_busno, PCI_SLOT(hose->first_busno),
> + PCI_FUNC(hose->first_busno), bar, bar_response);
> + }
Only PCI_BASE_ADDRESS_1 (aka PCIL0_PTM1BAR) needs to be set since PTM2
is disabled (Ash is already doing it this way). My reading of the
manual would indicate that the BAR ought to be set before PTM1 is
enabled, but haven't seen any problems with this.
Could enclose the early_read_config_dword() in #ifdef DEBUG.
Rainier (NP4GS3) PMM1 is setup specially in the existing code, is this
no longer needed?
This code is fragile and tends to break on certain platforms in ways
that can't be explained by the available documentation. I can help test
the unified version on Walnut/Sycamore/Ash if needed.
--
Todd
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-04 18:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 12:27 very minor 405GP and 405GPr PCI difference Ralph Blach
2002-09-30 4:01 ` David Gibson
2002-10-01 5:21 ` David Gibson
2002-10-01 8:37 ` "David Müller (ELSOFT AG)"
2002-10-02 1:42 ` David Gibson
2002-10-02 4:26 ` Allen Curtis
2002-10-02 5:34 ` David Gibson
2002-10-02 17:03 ` Matt Porter
2002-10-03 1:10 ` David Gibson
2002-10-03 15:14 ` Matt Porter
2002-10-04 2:48 ` David Gibson
2002-10-04 18:33 ` Todd Poynor [this message]
2002-10-08 4:17 ` David Gibson
2002-10-08 19:39 ` Todd Poynor
2002-10-09 2:14 ` David Gibson
[not found] ` <20021 <20021023040850.GC1198@zax>
2002-10-24 23:50 ` Ralph Blach
2002-10-25 1:19 ` David Gibson
2002-10-02 7:46 ` "David Müller (ELSOFT AG)"
2002-10-03 1:12 ` David Gibson
2002-10-03 8:28 ` "David Müller (ELSOFT AG)"
2002-10-06 5:23 ` Andrew May
2002-10-07 1:31 ` Matt Porter
2002-10-08 4:14 ` David Gibson
2002-10-08 5:21 ` Andrew May
2002-10-08 14:56 ` Matt Porter
2002-10-08 17:31 ` Andrew May
2002-10-08 18:20 ` Matt Porter
2002-10-09 1:58 ` David Gibson
2002-10-09 10:35 ` Kenneth Johansson
2002-10-09 15:21 ` Allen Curtis
2002-10-11 19:37 ` Andrew May
2002-10-14 1:20 ` David Gibson
2002-10-08 6:19 ` Allen Curtis
2002-10-08 15:18 ` Matt Porter
2002-10-09 2:10 ` David Gibson
2002-10-22 21:55 ` Todd Poynor
2002-10-23 4:08 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 13:10 Ralph Blach
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=3D9DDEE9.5070909@mvista.com \
--to=tpoynor@mvista.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.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 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.