The attached patch is a start at adding the internal peripherals of the MPC107/MPC8240/MPC8245 to the OCP bus. I've used thus in the 2.6 port of my MPC107 I2C driver, which follows shortly. I intend to use this for the DMA controller later, once I decide what device ID to give it.
I'm a little uncertain about OCP device IDs. Should there be a separate I2C device ID for each different I2C programming interface from the same vendor? Motorola have already given us two separate implementations on PowerPC. This is a little bit different from the PPC40x use of OCP, because it's hard to calculate everything at compile time. This is particularly caused by the pcore boards, which use the MPC107 but don't use the interrupt controller. I've compiled for pcore, lopec, sandpoint, and an in-house board without errors. PowerPMC250 was broken before, and I have probably not repaired it. Any comments? (I'm away from email midweek, so I may not answer until Friday.) - Adrian Cox Humboldt Solutions Ltd. -------------- next part -------------- A non-text attachment was scrubbed... Name: ocp.patch Type: text/x-patch Size: 8931 bytes Desc: Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20040614/ae046163/attachment.bin
