Re: [riot-devel] reserve main and let application define thread(s)

2015-02-17 Thread Ludwig Ortmann
Hi, On Sat, Feb 14, 2015 at 03:28:56PM +0100, Kaspar Schleiser wrote: On 02/14/15 12:28, Ludwig Ortmann wrote: I created quickdirty branches for both methods: plain c: https://github.com/LudwigOrtmann/RIOT/tree/wip/remove-main-application-init macro magic:

Re: [riot-devel] reserve main and let application define thread(s)

2015-02-14 Thread Ludwig Ortmann
Hi, On Sat, Feb 14, 2015 at 11:50:38AM +0100, Ludwig Ortmann wrote: On Fri, Feb 13, 2015 at 06:49:56PM +0100, Kaspar Schleiser wrote: On 02/13/15 15:55, Ludwig Ortmann wrote: My proposal: Let the application Makefile export one or possibly several names to be used for the initial

Re: [riot-devel] reserve main and let application define thread(s)

2015-02-14 Thread Joakim Gebart
On Sat, Feb 14, 2015 at 3:28 PM, Kaspar Schleiser kas...@schleiser.de wrote: Hi, On 02/14/15 12:28, Ludwig Ortmann wrote: I created quickdirty branches for both methods: plain c: https://github.com/LudwigOrtmann/RIOT/tree/wip/remove-main-application-init macro magic:

Re: [riot-devel] reserve main and let application define thread(s)

2015-02-13 Thread Oleg Hahm
Hi! My proposal: Let the application Makefile export one or possibly several names to be used for the initial application thread(s). kernel_init will then take care of creating those. The function name main will be reserved for boards/cpus to implement. In case of native/PsoC, the cpu's