Ok, i know what you mean, i will remove the old i2c driver in my latest version 
of i2c.

Best Regards
Sichen Zhao

________________________________________
From: devel <[email protected]> on behalf of Joel Sherrill 
<[email protected]>
Sent: Friday, May 26, 2017 23:12
To: Ben Gras
Cc: [email protected]
Subject: Re: GSOC student question

On May 26, 2017 9:59 AM, "Ben Gras" 
<[email protected]<mailto:[email protected]>> wrote:

Dear all,

On 05/22/2017 11:56 AM, Joel Sherrill wrote:


On Mon, May 22, 2017 at 10:11 AM, Gedare Bloom 
<[email protected]<mailto:[email protected]>> wrote:
I think the i2c was developed and tested only on the BeagleBone Black.
I don't think anyone has used the xm yet, though I could be mistaken.

Yes, I believe the old one should be replaced by the updated version.

This is likely a stupid question. Do we have confidence that the new i2c works
on all platforms that the old one did?

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.

Thanks Ben. That is precisely the information needed.


--joel

On Mon, May 22, 2017 at 9:04 AM, Sichen Zhao 
<[email protected]<mailto:[email protected]>> wrote:
> Hi all,
>
> I am working on my GSOC project- Beaglebone BSP projects
> There is a question, Is the code in beagle/misc/i2c.c for the beagle bone or
> for the beagle xm or other processor?
> I developed the i2c for Beaglebone Black(AM335X), So if i need remove the
> old one i2c.c in misc when i send the patch?
>
> Best Regards
> Sichen Zhao




_______________________________________________
devel mailing list
[email protected]<mailto:[email protected]>
http://lists.rtems.org/mailman/listinfo/devel


_______________________________________________
devel mailing list
[email protected]<mailto:[email protected]>
http://lists.rtems.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to