<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On May 26, 2017 9:59 AM, "Ben Gras" <<a href="mailto:beng@shrike-systems.com">beng@shrike-systems.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Dear all,<br>
</p><div class="quoted-text">
<br>
<div class="m_1613622509348823410moz-cite-prefix">On 05/22/2017 11:56 AM, Joel Sherrill
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, May 22, 2017 at 10:11 AM,
Gedare Bloom <span dir="ltr"><<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think
the i2c was developed and tested only on the BeagleBone
Black.<br>
I don't think anyone has used the xm yet, though I could
be mistaken.<br>
<br>
Yes, I believe the old one should be replaced by the
updated version.<br>
</blockquote>
<div><br>
</div>
<div>This is likely a stupid question. Do we have confidence
that the new i2c works</div>
<div>on all platforms that the old one did?</div>
</div>
</div>
</div>
</blockquote>
<br></div>
The previous i2c implementation in the beagle bsp never worked on
hardware, only to a limited degree in qemu; replacing it won't make
anything worse for anyone.<br></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Thanks Ben. That is precisely the information needed. </div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
<br>
<blockquote type="cite"><div class="quoted-text">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>--joel </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="m_1613622509348823410HOEnZb">
<div class="m_1613622509348823410h5"><br>
On Mon, May 22, 2017 at 9:04 AM, Sichen Zhao <<a href="mailto:zsc19940506@outlook.com" target="_blank">zsc19940506@outlook.com</a>>
wrote:<br>
> Hi all,<br>
><br>
> I am working on my GSOC project- Beaglebone BSP
projects<br>
> There is a question, Is the code in
beagle/misc/i2c.c for the beagle bone or<br>
> for the beagle xm or other processor?<br>
> I developed the i2c for Beaglebone Black(AM335X),
So if i need remove the<br>
> old one i2c.c in misc when i send the patch?<br>
><br>
> Best Regards<br>
> Sichen Zhao<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="m_1613622509348823410mimeAttachmentHeader"></fieldset>
<br>
</div><pre>______________________________<wbr>_________________
devel mailing list
<a class="m_1613622509348823410moz-txt-link-abbreviated" href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>
<a class="m_1613622509348823410moz-txt-link-freetext" href="http://lists.rtems.org/mailman/listinfo/devel" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/devel</a></pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br></div></div></div>