GSOC 2017

Hi All: I already finished the proposals on RTEMS GSOC wiki. Best Regards Sichen Zhao 发自 Outlook ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: PI STATUS

Hi Gedare I was looking at the ticket #2733(Related to your SPI issues) and potential project for GSoc 2017 for Raspberry Pi the one I find interesting is "Convert the existing SPI support to the new Linux SPI API and test with SPI devices". I have gone through the wordpress bolg(https://asuolgso

Re: timeouts and failure

On Sat, Mar 18, 2017 at 9:00 AM, Joel Sherrill wrote: > These are all long running tests. Gedare is on a new computer which I > assume is quite fast. So he has fewer timeouts. > > I am out of town but can try to remember to use tsim to get the running > time for some of these in real CPU time. My

Summer of Code Students - Please Read

Hi RTEMS has a template in Google Docs for proposals. It has permissions set such that anyone can access it and make a COPY to use as the starting point for their own proposal. You do NOT need write access to the proposal. You will need to share the proposal with RTEMS mentors, developers, and u

Re: timeouts and failure

These are all long running tests. Gedare is on a new computer which I assume is quite fast. So he has fewer timeouts. I am out of town but can try to remember to use tsim to get the running time for some of these in real CPU time. My recollection is that crypt01 takes a long time compared to other

Re: timeouts and failure

Gedare, By erc32 under gdb do you mean using --debug-trace=gdb option with rtems-test ? I ran a normal ./rtems-test --log=log_erc32_run_alltest_new --rtems-bsp=erc32-run --rtems-tools=$HOME/development/rtems/4.12 /home/thd/development/rtems/src/builds/b-erc32_allt/sparc-rtems4.12/c/erc32/testsuite