ERk.<br> So if I needed to read values from four i2c devices (raw access would be fine) and I need to get this working in a few days, how would you suggest I proceed? Kernel = 2.6.23+. <br><br> Do I need to start from scratch?
<br><br> Start by using Jon's patch (or are the 5200 i2c and the cpm2 i2c completely incompatible?) <br><br> What about other cpm2/i2c threads - Did they ever complete? <br> 1) On Wednesday, November 23, 2005 8:01 AM Kumar Gala wrote:
><i> Can we rename the driver from mpc8260 -> cpm2. The driver should work</i>
><i> on any device that has a "CPM2" which includes a number of MPC82xx</i>
><i> and MPC85xx <a class="kLink" id="KonaLink0" onmouseover="adlinkMouseOver(event,this,0);" style="position: static; text-decoration: underline ! important;" onclick="adlinkMouseClick(event,this,0);" onmouseout="adlinkMouseOut(event,this,0);" href="http://osdir.com/ml/ports.ppc.devel/2005-11/msg00153.html#" target="_top">
<font style="font-weight: 400; font-size: 10pt; color: blue ! important; font-family: Courier New; position: static;" color="blue"><span class="kLink" style="border-bottom: 1px solid blue; font-weight: 400; font-size: 10pt; color: blue ! important; font-family: Courier New; position: relative; background-color: transparent;">
processors</span></font></a>. So calling it and its config options, etc</i>
><i> MPC8260 is going to be confusing to users.</i>
[PATCH] I2C: Add I2C Bus support for MPC with CPM2.
<br><br><br> <br><br><br><div><span class="gmail_quote">On 11/14/07, <b class="gmail_sendername">Kumar Gala</b> <<a href="mailto:galak@kernel.crashing.org">galak@kernel.crashing.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The patch is orthogonal to your issue.<br><br>There is NOT a driver in the kernel tree for the i2c on CPM2 based<br>parts like the 8248 (from what I can tell).<br><br>- k<br><br>On Nov 14, 2007, at 9:31 AM, Alan Bennett wrote:
<br><br>> Does this patch support the cpm2 as well?<br>><br>> I get conflicting thoughts looking over the latest postings.<br>><br>> -Alan<br>><br>><br>> On 11/13/07, Jon Smirl < <a href="mailto:jonsmirl@gmail.com">
jonsmirl@gmail.com</a>> wrote:I am working on<br>> a patch for i2c and device tree. I attached the current version.<br>><br>> DTC entry looks like this.<br>><br>> i2c@3d40 {<br>> compatible = "mpc5200b-i2c","mpc5200-
<br>> i2c","fsl-i2c";<br>> reg = <3d40 40>;<br>> interrupts = <2 10 0>;<br>> interrupt-parent = <&mpc5200_pic>;
<br>> fsl5200-clocking;<br>><br>> rtc@51f {<br>> compatible = "epson,rtc8564";<br>> reg = <51>;
<br>> };<br>> };<br>><br>><br>><br>> --<br>> Jon Smirl<br>> <a href="mailto:jonsmirl@gmail.com">jonsmirl@gmail.com</a><br>><br>><br>> _______________________________________________
<br>> Linuxppc-dev mailing list<br>> <a href="mailto:Linuxppc-dev@ozlabs.org">Linuxppc-dev@ozlabs.org</a><br>> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-dev">https://ozlabs.org/mailman/listinfo/linuxppc-dev
</a><br><br></blockquote></div><br>