[riot-devel] Is RIOT right?

Hello everyone, we are developing an IOT application and we got impressed with RIOT. It sports some really nice features and it looks like there is a great community over here. On the paper RIOT seems to be perfect for our application, but we need to go deeper before we start investing our

Re: [riot-devel] RIOT for Zigduino

Hi, I think so far nobody has attempted to port that board. Please don't take the available porting guide word-by-word, it might be outdated in places - we are currently putting heavy effort in rewriting/updating our documentation! So for porting the Zigduino I think you can just follow a

Re: [riot-devel] Task Forces

Hi again, OK, I modified the page, here's how it would look like: https://github.com/RIOT-OS/RIOT/wiki/Task-Forces Comments/input welcome. Talking about task forces, was there not a LPM task force on the way too? Best, Emmanuel On Thu, Nov 19, 2015 at 4:59 PM, Kaspar Schleiser

Re: [riot-devel] Task Forces

Hey, On 11/19/15 16:50, Emmanuel Baccelli wrote: > - would Kaspar agree he was the shepherd of the timers task force? yes. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Task Forces

OK, I could go ahead and modify the wiki with some tentative text for that, which we could refine later on. In practice: - would Kaspar agree he was the shepherd of the timers task force? - would Martine & Hauke agree they were the shepherds of the nasty task force? - would Martine & Hauke

[riot-devel] DocTF - First meeting

Dear ritualizing IoTlers, this morning the first virtual meeting of the documentation task force (DocTF) took place. DocTF is chartered to improve the overall state of RIOT's documentation and particular work on high level descriptions of RIOT's architecture and its modules. Please find the

Re: [riot-devel] Task Forces

+1 here too. I think it is also important to describe to malloc and free :) I mean how to: 1 - create a new task force (hopefully we have a lot more to come!) 2 - join/ping/revive an existing task force (e.g. OTA is somewhat dormant) 3 - dissolve an existing task force For creating: how about,

Re: [riot-devel] Task Forces

Yes to both. 2015-11-19 17:54 GMT+01:00 Hauke Petersen : > > > On 19.11.2015 16:50, Emmanuel Baccelli wrote: > > OK, I could go ahead and modify the wiki with some tentative text for > that, which we could refine later on. > In practice: > > - would Kaspar agree he

[riot-devel] Task Forces

Dear respected IOTlers, for already quite some time the idea of having task forces is floating around in our community: small teams of RIOT developers that work together for some time towards a (more or less) well-defined goal. A good and very successful example for such a task force that

Re: [riot-devel] TI CC1310 and CC2650

Hi Adam,just the really low-level RF stuff is executed by the M0 RF core. I am not sure if the memory section that contains the code for the RF core is reprogrammable, the reference manual describes it as ROM [1, Chapter 1.1; 1.3.2.3]. From my understanding the code for the M0 RF core is stored in

Re: [riot-devel] Task Forces

Hey, On 11/19/15 14:48, Oleg Hahm wrote: > As an effort to "formalize" this idea of task forces a little bit more, I just > created a small page in the Wiki: > > What do you think? +1 I've updated the xtimer page. Kaspar ___ devel mailing list