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: <000001c437cd$52469fc0$d100000a@sbs2003.local> (raw)
In-Reply-To: Your message of "Tue, 11 May 2004 18:01:44 PDT." <20040511180144.A4901@home.com>
On Tue, 11 May 2004 18:01:44 PDT, Matt Porter said:
> Actually, OCP stands for On-Chip Peripheral and is the basic system
> we've used in ppc32 for some time now to abstract dumb peripherals
> behind a standard API. BenH did yet another rewrite of OCP in 2.4
> sometime ago and I picked up that work to port to 2.6 and the new
> device model. It is a software abstraction, and easily allows us to
> plug in SoC descriptors when new chips come out and use standard apis
> to modify device entries on a per-board basis during "setup_arch()
> time". It used to be PPC4xx-specific, but now is being used by
> PPC85xx, MV64xxx, and MPC52xx based PPC systems. "Now", meaning that
> the respective developers for those parts are using the OCP working
> tree to base their 2.6 ports off of.
Wrap a /* */ around that paragraph and add it to the top of ppc/syslib/ocp.c :)
** 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 [this message]
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
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='000001c437cd$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