Messages in this thread | | | From | <> | Subject | Re: [PATCH 1/2] PPC32: New OCP core support | Date | Wed, 12 May 2004 04:00:46 +0100 |
| |
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/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |