Re: [PATCH] api: Remove deprecated task variables

2016-02-29 Thread Sebastian Huber
Before we remove the task variables, all remaining use cases must be converted to use an alternative. On 01/03/16 04:46, Aun-Ali Zaidi wrote: Task variables were a feature of RTEMS' Tasks which functioned in the same way as POSIX keys and TLS. In addition to their scarce usage they are not

[PATCH] api: Remove deprecated task variables

2016-02-29 Thread Aun-Ali Zaidi
Task variables were a feature of RTEMS' Tasks which functioned in the same way as POSIX keys and TLS. In addition to their scarce usage they are not SMP safe. updates #2494. --- c/src/ada/rtems-tasks.adb | 65 --- c/src/ada/rtems-tasks.ads |

Re: x86_64 BSP as GSOC2016 project

2016-02-29 Thread Joel Sherrill
On Mon, Feb 29, 2016 at 2:00 PM, Saket Sinha wrote: > On Tue, Mar 1, 2016 at 1:14 AM, Saket Sinha > wrote: > > Hi, > > > > Congratulations to the coreboot team for selection in GSOC 2016. > > Sorry for the typo. I meant the RTEMS team. I worked

Re: RPC and RTEMS task variables

2016-02-29 Thread Joel Sherrill
On Mon, Feb 29, 2016 at 5:44 PM, Aun-Ali Zaidi wrote: > $ grep -lR "task_var" > .git/objects/pack/pack-97a9b54f14bf9a5b8987276468b6bf120d1f2ab4.pack > c/src/lib/libbsp/powerpc/mvme5500/vectors/exceptionhandler.c > c/src/lib/libbsp/powerpc/gen5200/include/bestcomm.h >

Re: RPC and RTEMS task variables

2016-02-29 Thread Aun-Ali Zaidi
$ grep -lR "task_var" .git/objects/pack/pack-97a9b54f14bf9a5b8987276468b6bf120d1f2ab4.pack c/src/lib/libbsp/powerpc/mvme5500/vectors/exceptionhandler.c c/src/lib/libbsp/powerpc/gen5200/include/bestcomm.h c/src/ada/rtems-tasks.adb cpukit/librpc/src/rpc/svc.c cpukit/librpc/src/rpc/rtems_rpc.c

Re: RPC and RTEMS task variables

2016-02-29 Thread Joel Sherrill
On Mon, Feb 29, 2016 at 4:56 PM, Aun-Ali Zaidi wrote: > Greetings, > > I am currently removing the deprecated task variables and am having issues > deciding on what to do with the use > of task variables in the RPC implementation. The next email will include a > patch of my

RTEMS Open Class in Huntsville March 14-18

2016-02-29 Thread Joel Sherrill
Hi Just a reminder that there will be an RTEMS Open Class here in Huntsville March 14-18. More details are here: http://rtems.com/trainingschedule If you are interested or have questions, feel free to ask me. Thanks. --joel ___ devel mailing list

RPC and RTEMS task variables

2016-02-29 Thread Aun-Ali Zaidi
Greetings, I am currently removing the deprecated task variables and am having issues deciding on what to do with the use of task variables in the RPC implementation. The next email will include a patch of my current tested and working progress. Any suggestions? Thanks, Aun-Ali Zaidi

Re: Participation in GSoC 2016

2016-02-29 Thread André Marques
Hello Jan and Deval, Às 20:24 de 29-02-2016, Jan Sommer escreveu: Hi, If you take a look here: https://devel.rtems.org/wiki/GSoC/2015#StudentsSummerofCodeTrackingTable you can find the links to the reports and repositories of the previous GSoC. Yurii Shevtsov was doing the work on the

Re: Participation in GSoC 2016

2016-02-29 Thread Jan Sommer
Hi, If you take a look here: https://devel.rtems.org/wiki/GSoC/2015#StudentsSummerofCodeTrackingTable you can find the links to the reports and repositories of the previous GSoC. Yurii Shevtsov was doing the work on the Ethernet/USB part for the pi. Andre Marques worked on the SPI and SD-Card

Re: x86_64 BSP as GSOC2016 project

2016-02-29 Thread Saket Sinha
Hi, Congratulations to the coreboot team for selection in GSOC 2016. I am interested in working on x86_64 BSP as GSOC2016 project with RTEMS and with initial guidance from Joel as to how to get started, I am working on the same. Looking forward to working with the community for the same.

Re: Participation in GSoC 2016

2016-02-29 Thread Deval Shah
It looks like there are more useful things in pipeline before raspberry pi cam support. Can anybody give me pointers/links to refer for porting ethernet support and SD card support? On Thursday 18 February 2016, soja-li...@aries.uberspace.de < soja-li...@aries.uberspace.de> wrote: > Am