From: <Valdis.Kletnieks@vt.edu>
To: <Administrator@vger.kernel.org>
Cc: <akpm@osdl.org>, <benh@kernel.crashing.org>,
<linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH 1/2] PPC32: New OCP core support
Date: Wed, 12 May 2004 04:00:46 +0100 [thread overview]
Message-ID: <000101c437cd$52469fc0$d100000a@sbs2003.local> (raw)
In-Reply-To: Your message of "Tue, 11 May 2004 17:01:50 PDT." <20040511170150.A4743@home.com>
On Tue, 11 May 2004 17:01:50 PDT, Matt Porter said:
> New OCP infrastructure ported from 2.4 along with several
> enhancements. Please apply.
Big honking patch. Wholesale removal of old code. Wholesale addition of
new code.
And this is the closest to a hint of what an OCP in the old code:
- * @device: OCP device such as PCI, GPT, UART, OPB, IIC, GPIO, EMAC, ZMII
- * @dev_num: ocp device number whos paddr you want
And in the new:
+extern struct ocp_def core_ocp[]; /* Static list of devices, provided by
+ CPU core */
And some vendor IDs that say that IBM and FreeScale make them, and Motorola
apparently rebadges/clones Freescale's (or vice versa)..
I'm *guessing* that this is some all-in-one integrated
north/south/PCI/east bridge with an APIC or similar and some I/O
controllers.... Or maybe it's a board-level designator like 'ebony'
seems to be.. or something..
It's a UART... or a Bus-level board.. or both.. ;)
arch/ppc/Kconfig says this:
config OCP
bool
depends on IBM_OCP
default y
that leads to arch/ppc/platforms/4xx/Kconfig:
config IBM_OCP
bool
depends on ASH || CPCI405 || EBONY || EP405 || OCOTEA || REDWOOD_5 || REDWOOD_6 || SYCAMOR
E || WALNUT
default y
Grepping for OCP in arch/ppc/platforms/4xx/* isn't informative either..
Color me mystified.. ;)
(Actually, other than the apparent lack of any comment that says what
an OCP in fact is, I didn't see any really big style problems while
scrolling through it..)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-12 2:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 0:01 [PATCH 1/2] PPC32: New OCP core support Matt Porter
2004-05-12 0:39 ` Valdis.Kletnieks
2004-05-12 1:01 ` Matt Porter
2004-05-12 1:10 ` Valdis.Kletnieks
2004-05-12 3:00 ` Valdis.Kletnieks
2004-05-12 13:32 ` Matt Porter
2004-05-12 3:15 ` Valdis.Kletnieks
2004-05-12 1:45 ` Matt Porter
2004-05-12 2:00 ` Matt Porter
2004-05-12 0:57 ` Andrew Morton
2004-05-12 1:06 ` Matt Porter
2004-05-12 1:45 ` Matt Porter
2004-05-12 2:38 ` Daniel Jacobowitz
2004-05-12 3:15 ` Daniel Jacobowitz
2004-05-12 1:30 ` Andrew Morton
2004-05-12 3:00 ` Valdis.Kletnieks [this message]
2004-05-12 3:15 ` Valdis.Kletnieks
2004-05-12 5:48 ` Christoph Hellwig
2004-05-12 6:15 ` Christoph Hellwig
2004-05-12 13:39 ` Matt Porter
2004-05-12 6:30 ` Christoph Hellwig
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='000101c437cd$52469fc0$d100000a@sbs2003.local' \
--to=valdis.kletnieks@vt.edu \
--cc=Administrator@vger.kernel.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox