<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=GB2312" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
LINE-HEIGHT: 1.5; FONT-FAMILY: ËÎÌå; COLOR: #000080; FONT-SIZE: 10.5pt
}
</STYLE>
<META name=GENERATOR content="MSHTML 8.00.6001.19412"></HEAD>
<BODY style="MARGIN: 10px">
<DIV>Hi, Rempel Cynthia,</DIV>
<DIV>Thanks for your advice.</DIV>
<DIV> </DIV>
<DIV>When I think about this project recently, some problem occur. I think the
major is how to test the driver. I have a ARM board, I can test the CAN driver,
but others donot. </DIV>
<DIV> </DIV>
<DIV>Can4linux is widely used on Linux, but is there a copyright problem?
for can4linux and RTEMS?</DIV>
<DIV> </DIV>
<DIV>And i also have some question on qemu-system-arm, does it support CAN? I
googled Wire-shark, i think it's a tool for TCP/IP stack, does it support CAN
too?</DIV>
<DIV> </DIV>
<DIV>I look forward to your help. Thanks in advance.</DIV>
<DIV> </DIV>
<HR style="WIDTH: 210px; HEIGHT: 1px" align=left color=#b5c4df SIZE=1>
<DIV><SPAN>jinyang.sia</SPAN></DIV>
<DIV> </DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV
style="PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKGROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B> <A href="mailto:cynt6007@vandals.uidaho.edu">Rempel,
Cynthia</A></DIV>
<DIV><B>Date:</B> 2013-04-19 11:58</DIV>
<DIV><B>To:</B> <A
href="mailto:jinyang.sia@gmail.com">jinyang.sia</A></DIV>
<DIV><B>CC:</B> <A
href="mailto:rtems-devel@rtems.org">rtems-devel</A></DIV>
<DIV><B>Subject:</B> RE: GSoC 2013</DIV></DIV></DIV>
<DIV>
<DIV>Hi Jinyang Sia,</DIV>
<DIV> </DIV>
<DIV>Thanks for asking for my feedback... the CAN protocol is indeed in wide use for communications, and would be a great asset for rtems users...</DIV>
<DIV> </DIV>
<DIV>If you get accepted, I look forward to testing out your driver... :) I'll probably see if I can get qemu-system-arm to network and use Wire-shark to detect CAN packets... Can4linux does look really interesting...</DIV>
<DIV> </DIV>
<DIV>It may be worth looking at the possibility of porting it or another CAN driver to RTEMS, using either examples-v2 or rtems-addon-packages as a guide... Although using existing code sometimes leads to upstreaming issues, it typically provides much of the work completed, and comes with tests (testing is very important, and I'm glad you mentioned it in your proposal :)... If you do need to patch the code to make it work on RTEMS it would be easier to maintain, if you could upstream the patches...</DIV>
<DIV> </DIV>
<DIV>The challenge then becomes identifying the best driver for the purpose, learning how to port things to RTEMS, upstreaming patches, and finally getting ready to document the driver for use and maintenance (basically doing a wiki page explaining how to use it, and further steps for a GSoC student next, or later, summer).</DIV>
<DIV> </DIV>
<DIV>Hope this helps!</DIV>
<DIV>Cynthia Rempel</DIV>
<DIV> </DIV>
<DIV>________________________________________</DIV>
<DIV>From: jinyang.sia [jinyang.sia@gmail.com]</DIV>
<DIV>Sent: Wednesday, April 17, 2013 7:54 PM</DIV>
<DIV>To: Rempel, Cynthia</DIV>
<DIV>Cc: rtems-devel</DIV>
<DIV>Subject: GSoC 2013</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV>Thanks. I have tried many times, i really don't understand why it doesn't work :-(. May be the last last email attachment, which contains two attachments, can work. It sent when Wed, 17 Apr 2013 22:17:35 +0800.</DIV>
<DIV> </DIV>
<DIV>I have wirte a proposal for this. Could you send your gmail to me, and i can shared with you. Hope to get some advice.</DIV>
<DIV> </DIV>
<DIV>________________________________</DIV>
<DIV>jinyang.sia</DIV>
<DIV> </DIV>
<DIV>From: Rempel, Cynthia<mailto:cynt6007@vandals.uidaho.edu></DIV>
<DIV>Date: 2013-04-18 10:30</DIV>
<DIV>To: jinyang.sia<mailto:jinyang.sia@gmail.com>; rtems-devel<mailto:rtems-devel@rtems.org></DIV>
<DIV>Subject: RE: GSoC 2013</DIV>
<DIV>Hi Jinyang Sia,</DIV>
<DIV> </DIV>
<DIV>Wow, the CAN driver sounds really useful!</DIV>
<DIV>Could you send the hello, world screenshot as a .pdf, .bmp, or .tif?</DIV>
<DIV>I tried to change the file you sent as a .txt to a .png and it didn't work...</DIV>
<DIV> </DIV>
<DIV>Once you do that could you please add yourself to the table at</DIV>
<DIV>http://wiki.rtems.org/wiki/index.php/RTEMSSummerOfCode and tell us some more about your project?</DIV>
<DIV> </DIV>
<DIV>-Cynthia Rempel</DIV>
<DIV>________________________________________</DIV>
<DIV>From: rtems-devel-bounces@rtems.org [rtems-devel-bounces@rtems.org] on behalf of jinyang.sia [jinyang.sia@gmail.com]</DIV>
<DIV>Sent: Wednesday, April 17, 2013 7:48 AM</DIV>
<DIV>To: rtems-devel</DIV>
<DIV>Subject: GSoC 2013</DIV>
<DIV> </DIV>
<DIV>Hi,</DIV>
<DIV>Sorry for the emails, some error occurs when I try to add attachments using the Foxmail. The screenshot still work if you change the extention to .png. And i try to send a email again use the google server, opps, some errors occur again. I do know what happens. sorry for the truobles.</DIV>
<DIV> </DIV>
<DIV>I want to particiapte in the GSoC2013, and i want to add a CAN driver and CAN API including interface for low level interface.</DIV>
<DIV> </DIV>
<DIV>CAN bus originally developed for automotive applications, but now it has widely used in other areas of industry, such as medical devices, agriculture vehicles, maritime, factory automation, process automation, etc. RTEMS, as a real-time embedded system, is also widely used in such areas. What i want to do is to develop a CAN driver for RTEMS, and also a whole CAN API, stack and low level driver interface.</DIV>
<DIV> </DIV>
<DIV>Hope it works.</DIV>
<DIV> </DIV>
<DIV>________________________________</DIV>
<DIV>jinyang.sia</DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></BODY></HTML>