Thanks Martine. Who is available to accompany Martine Saturday at 8PM at
C-Base?
(I will try to attend myself, but I cannot confirm yet, thus the above
question ;)
Cheers
Emmanuel
On Thu, Oct 30, 2014 at 1:44 PM, Martine Lenders mlend...@inf.fu-berlin.de
wrote:
Am 30. Oktober 2014 13:35 schrieb
Hi everyone,
this is a gentle reminder to input your opinions on this thread before
Wednesday night (i.e., tomorrow).
Thanks,
Emmanuel
On Tue, Dec 9, 2014 at 12:43 AM, Carsten Bormann c...@tzi.org wrote:
On 09 Dec 2014, at 00:09, Adam Hunt voxa...@gmail.com wrote:
allow a potential license
Hi Johann,
Le 12 déc. 2014 00:48, Johann Fischer johann_fisc...@posteo.de a écrit :
Can you explain exactly what you expect of licence change? That more
hardware
will be supported? That RIOT will be more spread?
The motivation for a more permissive license now is that the RIOT community
has
Hi Olaf,
if both LGPL and other considered licenses are OK for you, then switch to
RIOT right now ;)
What is holding you back, more precisely? I would be interesting to know
about it, it might bring some arguments to this debate.
Best,
Emmanuel
Le 11 déc. 2014 18:28, Olaf Bergmann
Hi Kaspar,
On Tue, Dec 16, 2014 at 11:28 AM, Kaspar Schleiser kas...@schleiser.de
wrote:
As the man earning a shit load of money from one of these evil companies,
using a proprietary smart phone, and buying Facebook goggles, working on
RIOT for me is a very expensive hobby.
I'm not sure I
be an awesome step, especially
for small design companies like us.
Thanks,
Akshay
On 4 December 2014 at 03:29, Emmanuel Baccelli emmanuel.bacce...@inria.fr
wrote:
Dear RIOTers,
we have been receiving an increasing amount of negative feedback from
various companies concerning the practical
May 2015 be inspiring for all RIOTers, as was 2014!
Cheers,
Emmanuel
Le 31 déc. 2014 00:34, Thomas Eichinger thomas.eichin...@fu-berlin.de
a écrit :
Thank you all for an amazing year with RIOT!
Looking forward to an exciting year 2015.
Best wishes to you all.
Thomas
On 24 Dec 2014, at
Hi Kaspar,
On Fri, Feb 20, 2015 at 12:24 PM, Kaspar Schleiser kas...@schleiser.de
wrote:
Hey Matthias,
On 02/19/15 23:47, Matthias Waehlisch wrote:
As you pointed out in your email, there are scenarios where the
approach will not help due to technical reasons (and using a weird
Hi Matthias,
On Thu, Feb 19, 2015 at 11:47 PM, Matthias Waehlisch
m.waehli...@fu-berlin.de wrote:
Hi Kaspar,
sorry for the silence!
As you pointed out in your email, there are scenarios where the
approach will not help due to technical reasons (and using a weird
compiler might have
Hi all,
I will probably join too.
Cheers
Emmanuel
On Thu, Jan 29, 2015 at 1:31 PM, Frank Holtz frank-riot2...@holtznet.de
wrote:
Hi,
i have joined this meeting.
Frank
Am 29.01.2015 11:48, schrieb Hauke Petersen:
Hi,
sounds interesting, I think I will go. Anyone joining in?
Cheers,
Hi Jan,
As far as I understood it, Ubuntu contacted us because they were looking
for expertise on how to communicate with embedded devices which cannot run
Linux.
A low-overhead solution that we suggested for their problem is: RIOT (and
its network stack) runs simultaneously on IoT devices, and
On Mon, Jan 5, 2015 at 6:06 PM, Ludwig Ortmann ludwig.ortm...@fu-berlin.de
wrote:
Hi,
On Mon, Jan 05, 2015 at 06:00:34PM +0100, Oleg Hahm wrote:
Maybe we can discuss a tentative schedule and set some milestones for the
refactoring during a (PlaceCam) conf call this week? What do you think?
Hi Baptiste,
I don't think there is a meeting today. Last week was heavy with the
network stack task force workshop, so if I understood correctly, this
week's meeting is cancelled.
Best,
Emmanuel
On Wed, Feb 11, 2015 at 9:56 AM, Baptiste Clenet bapcle...@gmail.com
wrote:
Hi,
Is there a
On Tue, Mar 17, 2015 at 4:31 PM, Ken Bannister kb...@runbox.com wrote:
Oleg,
There's definitely a need for generic MAC layer solutions in RIOT,
besides the
specific solutions like CSMA in the cc110x driver or TiSCH for 802.15.4e
as
part of the OpenWSN stack. As far as I know, at least
Dear all,
thanks for the input from everyone on this topic. It is a tough case to
decide, based on our long and detailed exchanges on this subject.
But it is probably time to conclude. At INRIA, we came up with the
following observations:
- there is no enthusiastic majority for a license change
wrote:
We have been getting quite a lot of students introducing themselves on the
mailing lists now. How many students can be accepted? Who decides on which
students are accepted? Google or RIOT?
Best regards, Joakim
On Mar 4, 2015 4:41 PM, Emmanuel Baccelli emmanuel.bacce...@inria.fr
wrote
Hi Thomas,
there are some initial efforts on-going in the community, such as [1] [2]
[3], and upcoming GSOC projects on implementing LWM2M amd dynamic linking.
However, this is not sufficient to get the whole nine yards. To have the
full picture, there lacks security/crypto aspects, software
Hi everyone,
I was recently in contact with Wakaama [1] community (part of the Eclipse
IoT foundation), and which maintains an open source implementation of LWM2M.
More to the point, they told me that the code base [3] is deprecated (it
was their repo prior to joining Eclipse), and that their
Hi everyone!
We now have a confirmed time and location for the next network stack task
force meeting: we will meet Thursday April 30th in the morning, from 10:00
to 12:00 CEST, in room 049 of the computer science building of FU Berlin
(Takustr. 9 | 14195 Berlin).
The tentative agenda with a list
Dear RIOTers,
we are happy to announce that three students have been selected to work on
RIOT in the context of Google Summer of Code (GSOC) 2015, which runs from
now until end of August.
Please welcome Alexandru Caciulescu, James Hollister and Kushal Singh.
Kushal will work on dynamic linking
Hi Lotte,
there was a slight delay due to technical issues. But the meeting is on now
(and you are in it ;).
Everyone else: feel free to join.
Best
Emmanuel
On Thu, Apr 30, 2015 at 10:13 AM, Lotte Steenbrink
lotte.steenbr...@fu-berlin.de wrote:
Hi,
afaik the meeting was supposed to start at
Hi everyone,
concerning the name of the new network stack, and assuming it is not going
to be the only network stack that RIOT hosts, here's a suggestion.
The way I see it, the goal of this network stack was/is to be generic [1]:
- one-size-fits-most
- flexible/configurable/extendable
In
Hi Julien
does it still do that for you? On my end, it works perfectly well.
Best,
Emmanuel
On Thu, Apr 2, 2015 at 3:27 PM, Julien Vermillard jvermill...@gmail.com
wrote:
Hi,
I tried to consult this mailing list archives, but the archive link on
this page:
2015, at 17:47, Emmanuel Baccelli emmanuel.bacce...@inria.fr
wrote:
Hi Lucas,
looks like a good opportunity. Do you know the organizers? To propose a
talk on RIOT, should we just use the online form, or should we first
contact someone in particular (one of the organizers you might happen
it seems a lot of people still do not understand important aspects of IoT...
http://www.zdnet.com/article/only-half-of-enterprise-developers-are-ready-for-the-internet-of-things-survey-finds/
___
devel mailing list
devel@riot-os.org
Seems Cortex M based, rather small and full of sensors
http://www.silabs.com/products/sensors/Pages/environmental-biometric-sensor-puck.aspx
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Dear RIOTers,
plans are shaping up towards a new RIOT release this month, driven by the
upcoming availability of the refactored network stack some of us have been
working on lately (code-named the gnrc stack, where gnrc stands for
generic, shortened by eliding vowels)
The envisioned schedule is
to the evolution of
both the community and of the work to be done
So this would be the place to talk about this and design this evolution
together.
Best,
Emmanuel
Cheers,
Martine
Am 28.05.2015 00:09 schrieb Kaspar Schleiser kas...@schleiser.de:
Hey,
On 05/28/15 00:02, Emmanuel Baccelli
soonish some input on the tentative definition of what a
task force is (and what it is not).
Best,
Emmanuel
On Thu, May 28, 2015 at 3:59 PM, Emmanuel Baccelli
emmanuel.bacce...@inria.fr wrote:
On Thu, May 28, 2015 at 7:53 AM, Oleg Hahm oliver.h...@inria.fr wrote:
Hi!
- introducing
Hi everyone,
I propose to launch a task force focusing on open processes at work in the
RIOT community. The goals are both (i) maintenance/improvements of these
processes to adapt to the evolution of our community, and (ii) ensure an
appropriate level of transparency concerning what the current
Hi Joakim,
GSOC students will start this month and will work until August -- hopefully
they will have so much fun that they will stick with the community
afterwards too ;)
During their work, GSOC students are supposed to interact with the
community at various levels, so the plan is it will be
+1
On Mon, Aug 24, 2015 at 5:50 PM, rakendra thapa rakendrath...@gmail.com
wrote:
+1
On Aug 24, 2015 9:13 PM, Oleg Hahm oliver.h...@inria.fr wrote:
Hi again!
So, are there any objections about putting the following into the Wiki?
=
## Guidelines for creating a good Pull Request
*
One argument for decently documented/explained code is that it is not only
for the reviewer(s) before merging, but for ALL the people who will look at
the code and try to understand/modify/extend it AFTER it's been merged...
That's potentially a LOT of people... and a lot of problems down the
+1 for disabling (unless Philipp yells very loud now ;)
On Tue, Nov 17, 2015 at 1:49 PM, Oleg Hahm wrote:
> Hi,
>
> since the results of both Strider CI systems are currently of very limited
> use and confusing for many people, I decided to deactivate them for now. If
>
Hi there,
I don't know about 101 or no 101 (although maybe it's too american centric
an expression, indeed, so I'd vote for another title).
But I do support some explicit policy as to how to contribute documentation
to RIOT.
The hope is that it will diminish duplicate documentation, and thus
Hi there,
I agree that some text would be very helpful. Actually, the plan was to
indeed provide some such text very soon, right Martine?
Best,
Emmanuel
On Tue, Nov 17, 2015 at 11:03 AM, Kaspar Schleiser
wrote:
> Hey Martine,
>
> On 11/17/15 09:18, Martine Lenders wrote:
>
Yay!
On Sun, Sep 27, 2015 at 11:16 PM, Oleg Hahm wrote:
> Dear roaring IOTlers,
>
> we've finally merged all remaining PRs that were missing for our upcoming
> release and are now in final testing phase. Therefore, I created a release
> branch [1] as well as a tag for the
gt; wrote:
>
>> wohoooah!
>>
>>
>> -Original Message-
>> From: Emmanuel Baccelli <emmanuel.bacce...@inria.fr>
>> To: RIOT OS kernel developers <devel@riot-os.org>
>> Sent: Mo., 05 Okt. 2015 23:11
>> Subject: Re: [riot-d
YAY!
On Mon, Oct 5, 2015 at 10:55 PM, Martine Lenders
wrote:
> \o/ finally!
>
> /goes to bed
> Am 05.10.2015 22:17 schrieb "Oleg Hahm" :
>
>> Dear RIOT developers and users,
>>
>> it has been a long and rocky road, but thanks to the marvellous
>>
+1
On Thu, Sep 17, 2015 at 8:02 PM, Ludwig Knüpfer <
ludwig.knuep...@fu-berlin.de> wrote:
> Hi,
>
> I bow my head to everyone who contributed :)
>
> Cheers,
> Ludwig
>
> Am 17. September 2015 18:31:21 MESZ, schrieb Oleg Hahm <
> oliver.h...@inria.fr>:
> >Ladies and gentlemen!
> >
> >I'm more
Hi everyone,
while so far most of us here are interested in shorter range radios (as far
as I know), there is this recent push towards low-power long-range
technologies of various types. I stumbled over this blunt, high-level
survey [1] of the current state of affairs in that domain, I thought it
Hi everyone,
here's what some people say looking back at 2015 [1].
If what is stated there is true, it may be one more hint we're on good
tracks at all levels, even license-wise?
Cheers,
Emmanuel
[1] http://www.zdnet.com/article/linux-and-open-source-have-won-get-over-it/
kas...@schleiser.de>
wrote:
> 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
&g
!
>
> Sounds like a sensible proposal to me.
>
> Cheers,
> Oleg
>
> Am Thu, Nov 19, 2015 at 03:51:36PM +0100 schrieb Emmanuel Baccelli:
> > +1 here too.
> > I think it is also important to describe to malloc and free :)
> > I mean how to:
> >
> > 1 - c
+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,
in good condition and send it as a pull request.
>
> > 2016-06-07 12:58 GMT+02:00 Emmanuel Baccelli <emmanuel.bacce...@inria.fr
> >:
> >
> > > Hi Gustavo, Hi Ivan,
> > > ok I see. thanks for your answers.
> > > That's too bad. It would have been gr
2016-05-31 17:30 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com
> >:
> > >
> > > > Hello Baptiste, Emmanuel
> > > >
> > > > I'll let the people more familiar (in cc) with it reply.
> > > >
> > > > On terça-feira, 31 de maio
2016-05-30 21:07 GMT+02:00 Emmanuel Baccelli <emmanuel.bacce...@inria.fr>:
>
>> Hi Baptiste,
>>
>> Thanks for the clarification.
>>
>> Have you already been in contact personally with Thiago?
>>
>> It may be interesting if they attend and/or pr
Hi there
I don't know how complete and up to date that is but there is also:
https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
Howto
Cheers
Emmanuel
On Jun 20, 2016 4:39 PM, "Francisco Javier Acosta Padilla" <
francisco.aco...@inria.fr> wrote:
> Hi Clark!
>
>
Caeveat: coma at the end url may mess up your automatic URL detection
thingie:
https://github.com/RIOT-OS/RIOT/wiki/Using-the-Eclipse-IDE-for-C-and-CPP-Developers,-
Howto
On Jun 20, 2016 4:49 PM, "Emmanuel Baccelli" <emmanuel.bacce...@inria.fr>
wrote:
> Hi there
>
>
Yay!
On Sun, Jan 10, 2016 at 4:28 PM, Cenk Gündogan
wrote:
> Dear RIOT developers and users,
>
> I am glad to announce the sixth official release of the RIOT operating
> system:
>
> --- * RIOT 2015.12 *
> ---
>
Hey there,
+1 for the idea on my side too.
cheers
Emmanuel
On Tue, Jan 19, 2016 at 12:45 PM, Kaspar Schleiser
wrote:
> Hey,
>
> On 01/19/2016 11:58 AM, Joakim Nohlgård wrote:
>
>> I would like to hear any ideas and opinions on this list on how to
>> effectively implement
Hi there,
thanks for your interest! Please have a look at
https://github.com/RIOT-OS/RIOT/wiki/GSOC16
Thanks,
Emmanuel
On Tue, Feb 16, 2016 at 8:01 AM, Aditya Manglik
wrote:
> Hello developers
> I would like to contribute to RIOT OS as a Google Summer of Code
>
Hi Satyaki,
thanks for your interest. Please have a look at
https://github.com/RIOT-OS/RIOT/wiki/GSOC16
Thanks,
Emmanuel
On Tue, Feb 16, 2016 at 9:41 AM, Satyaki Upadhyay
wrote:
> Hi
>
>
> My name is Satyaki and I'm a newcomer to the RIOT community. I want to
> contribute
Fantastic! Let's keep rocking!
On Mon, Feb 22, 2016 at 6:33 AM, Ludwig Knüpfer <
ludwig.knuep...@fu-berlin.de> wrote:
> Hoorah!
>
> BTW:
> what's the current SLoC count?
>
> Cheers,
> Ludwig
>
> Am 22. Februar 2016 00:56:13 MEZ, schrieb Kaspar Schleiser <
> kas...@schleiser.de>:
> >Hey fellow
Hi there,
I think it would be great to have a RIOT tutorial space somewhere. Two
comments:
- Cenk also had some input on that at
https://github.com/cgundogan/RIOT-Tutorial
- maybe some stuff from Alex (e.g. his upcoming Bluetooth+802.15.4 border
router) could belong into applications or even
Hi Baptiste,
I think you need to specify for what type of use/product.
Else it's difficult to judge...
I mean: if RIOT is supposed to "make coffee and donuts out of the box",
it's maybe not production ready.
For some other types of use, it may be production-ready.
Cheers,
Emmanuel
On Wed, Mar
Hi everyone,
our friends from Eclipse Foundation are conducting a survey about IoT
technologies currently in use or aimed at in various contexts. Maybe you
can consider filling it in (and maybe the results will be of some interest).
https://www.surveymonkey.com/r/AGILEIoT
Best,
Emmanuel
Thanks Oleg! Now we're super legit ;)
On Fri, Mar 18, 2016 at 4:16 PM, Oleg Hahm wrote:
> Dear requesting IOTlers,
>
> good things come to those who wait: we finally got our letsencrypt [1]
> sponsored certificates for the self-hosted RIOT related pages.
> For
Hi Om
RIOT is not participating in GSOC this year.
Best,
Emmanuel
On Tue, Mar 8, 2016 at 4:20 PM, Om Shivom Nagpal
wrote:
> Hi, I am Om Shivom pursuing CSE from PEC University of Technology,
> Chandigarh and I have previously worked on C++ and Python. I am interested
>
this branch might give
> you a head start? Feel free to copy what you need!
>
> Cheers,
> Hauke
>
> [1] https://github.com/haukepetersen/RIOT/tree/add_board_stm32f7discovery
>
> On 03.03.2016 18:31, Emmanuel Baccelli wrote:
>
> Hi Antoine,
>
> As far as I know, no
Hi Antoine,
As far as I know, no one has started porting to this board, or to any other
Cortex M7-based board yet.
However, it would be great to have support for this Discovery board (and
initial M7 support).
Are you interested/willing to start porting?
The community usually turns out to be
<mich...@steelcode.com>
wrote:
> I would be more than happy to start it up again and maintain it if it
> would be of use to the community. I'll do so as soon as I finish my
> post-IPSN Vienna tour :)
> On Apr 21, 2016 3:46 PM, "Emmanuel Baccelli" <emmanuel.bacce..
On Wed, May 11, 2016 at 12:26 PM, Oleg Hahm wrote:
> Hi Matthias!
>
> On Wed, May 11, 2016 at 12:12:42PM +0200, Mathias Tausig wrote:
> > The interafces used by the cryptographic digest functions sha256, sha1
> and md5
> > (xx_init, xx_update, xx_final) are very
at 2:43 PM, Michael Frey <f...@informatik.hu-berlin.de>
wrote:
> Hi,
>
> Am Di, 15.03.2016, 11:15, schrieb Emmanuel Baccelli:
>
> > https://www.surveymonkey.com/r/AGILEIoT
>
> so, here are (if I see this correctly) are the results
>
>
> https://ianskerrett.wor
Hi Ken
Let me enquire. It would be great if you could participate indeed.
Cheers
Emmanuel
On Jul 14, 2016 7:12 PM, "Ken Bannister" wrote:
> I read that Ari Keränen and Carsten Bormann plan to lead a discussion on
> Saturday at the RIOT Summit on the Web and IoT, including
Hi again,
for the CoAP session on Saturday, there may be a remote participation
organized based on Google Hangouts or some other WebRTC scheme. Stay
tuned... Carsten will make the announcement will be on #riot-os
Cheers
Emmanuel
On Thu, Jul 14, 2016 at 7:47 PM, Emmanuel Baccelli <
emmanuel.ba
Hi Carsten,
Great. Thanks,
Emmanuel
On Thu, Jul 14, 2016 at 10:47 PM, Carsten Bormann <c...@tzi.org> wrote:
> Emmanuel Baccelli wrote:
> > The CoAP discussion is going to be a break-out session on Saturday, with
> > a relatively small number of participants, so remot
Hi Joakim,
unfortunately, there is no such plan concerning the whole event...
The CoAP discussion is going to be a break-out session on Saturday, with a
relatively small number of participants, so remote participation would be
easier to organize.
Best,
Emmanuel
On Thu, Jul 14, 2016 at 10:08
Jul 15, 2016 at 10:44 AM, Oleg Hahm <oliver.h...@inria.fr> wrote:
>
>> +1
>>
>> On Fri, Jul 15, 2016 at 09:35:06AM +0200, Emmanuel Baccelli wrote:
>> > Thanks Carsten!
>> >
>> > On Jul 15, 2016 9:30 AM, "Carsten Bormann&q
Hi Arash,
at first sight Linux can run on C.H.I.P.
So why not use Linux?
RIOT targets devices which cannot run Linux (or derivatives/equivalents).
Hence: there are no plans to support CHIP
best,
Emmanuel
On Wed, Jul 20, 2016 at 10:29 AM, Arash Shafiei wrote:
> Hi, I was
Thanks Carsten!
On Jul 15, 2016 9:30 AM, "Carsten Bormann" wrote:
>
> https://hangouts.google.com/hangouts/_/bomthsflordmhfhplund2imm64e
>
> You cannot see the slides there; copies of the slides are slowly
> gathering at http://www.tzi.de/~cabo/riot-summit/
>
> If you join the
Hi Chen,
RIOT targets primarily low-end IoT devices, e.g. see devices defined in RFC
7228 [1].
At first sight, it seems to me your hardware is rather high-end in
comparison: what are the RAM/ROM specs? What architecture? If it can run
Linux, why don't you want to use Linux?
This does not mean
Hi everyone,
I just stumbled across this.
Seems Arduino is going for easier hardware modularity and cloudification.
https://techcrunch.com/2016/09/29/arduino-unleashes-a-serious-internet-of-things-system-for-hardware-hackers/
Emmanuel
___
devel
OK, I just created the label. So feel free to use it this month!
We'll delete the label after our next release.
Cheers,
Emmanuel
On Fri, Oct 7, 2016 at 2:53 PM, Kaspar Schleiser <kas...@schleiser.de>
wrote:
> Hey,
>
> On 10/07/2016 02:50 PM, Emmanuel Baccelli wrote:
> > A
Hi Srivignessh,
improving x86 support in RIOT is a not such a bad idea, in my opinion.
If you are interested in this however, instead of the Galileo board, I
would suggest working on support for Arduino 101 [1].
The first step would be to provide initial support i.e. to have the bare
minimum for
Hi there,
Any news on this?
Is there a branch available somewhere?
Best,
Emmanuel
On Mon, Jun 20, 2016 at 3:20 PM, Anon Anonymous
wrote:
> Hi, RIOTers!
>
> After a couple of months I've finished a Semtech's SX1276 LoRa transceiver
> driver (physical level, RX and TX)
Hello again Cr0s,
Great. I was asking this because some RIOTers in Chile are about to start
to port LoRaWAN to RIOT, hence your SX1276 driver would be great for them,
I guess.
Looking forward to your PR!
One last question: are you using your SX1276 on a STM32L1 of some sort?
Cheers
Emmanuel
Hi Mattia,
I would say: make the PR and we will feedback then. Two comments at first
sight, though:
- to remain clean, Apache licensed files should not be PRed directly to be
located in the RIOT/example/
Instead, can't you pull them (+ whatever you need) along with your pkg?
- the files you
Yay! Thanks a bunch Martine for taking on the role of manager for this
release.
Congrats to everyone for all the work!
Emmanuel
On Fri, Nov 11, 2016 at 4:21 PM, Kaspar Schleiser
wrote:
> Hey,
>
> congratulations to everyone and thanks for all the hard work!
>
> On
Hi Akshay
It seems that SiLabs uses the terms of a zlib license [1] for its code (see
[2]).
If this is correct indeed, zlib is recognized by FSF and compatible with
LGPL, so no issues there, I guess.
Cheers
Emmanuel
[1] https://en.wikipedia.org/wiki/Zlib_License
[2]
rts. The only real change required on Mac
> OS X was to include instead of when
> building with RIOT_OS.
> >
> >
> > Warm Regards,
> >
> > Kaleb Himes
> > Software Engineer
> > www.wolfssl.com
> >
> >> On Dec 8, 2016, at 09:13, Emman
+1 here! This would be a great addition to RIOT.
Cheers,
Emmanuel
On Dec 1, 2016 12:38 AM, "Matthias Waehlisch"
wrote:
> Hi Kaleb,
>
>
> +1 -- in particular, if you plan to continue the maintenance of the
> port!
>
>
>
> Cheers
> matthias
>
>
> On Wed, 30 Nov 2016,
Hi Rafał
On Thu, Jan 5, 2017 at 2:15 PM, Rafał Rzatkiewicz <
rafal.rzatkiew...@gmail.com> wrote:
>
>
> https://github.com/RIOT-OS/RIOT/issues/2493
>
> Of course this checklist is related to the previous implementation of RIOT
> OS and long before the gnrc network stack which is included in
Hi François,
you could first try the below, assuming you have some other board with
802.15.4 lying around (e.g. a SAMR21):
- use gnrc_minimal on your waspmote
- compile/flash/term the gnrc_networking example on the other board
- ping6 on the board running the gnrc_networking example to check that
Hi everyone,
those concerned with software updates in RIOT should probably consider
registering to this new mailing list to follow and/or participate in
related discussions: https://www.ietf.org/mailman/listinfo/fud
Cheers,
Emmanuel
___
devel mailing
Hi Ken,
yes there is. It is planned in September, in Berlin.
The dates are not 100% set in stone, but very probably it will be Sept.
29th and 30th, in conjunction with ACM ICN conference [1].
We will announce it soon.
Would you be able to come by? Would be great.
Cheers,
Emmanuel
[1]
Hi everyone,
there was a seminar organized earlier this month in Paris. The goal of that
seminar was to gather various research teams working (or considering to
work) around RIOT at Inria.
The agenda + slides are available at http://riot-os.org/seminar-2017.html
Some synopsis/highlights below:
Yay! Thanks Kaspar for being the Release Manager this time around!
Best,
Emmanuel
On Wed, May 10, 2017 at 1:04 PM, Kaspar Schleiser
wrote:
> Dear RIOTers,
>
> we are happy to announce the 11th official release of RIOT:
>
> --- * RIOT 2017.04 *
Hi Joakim,
FYI I just got hold of some kw41z boards.
gnrc_networking compiles on both OS X and Ubuntu (Vagrant).
Now I am trying to debug some trouble with jlink (can't flash the board
yet).
Cheers
Emmanuel
On Thu, Jun 8, 2017 at 1:09 PM, Emmanuel Baccelli <
emmanuel.bacce...@inria.fr>
Hi Joakim
just the other day, we ordered a couple frdm-kw41z at Inria, so we should
be able to test here soon.
Cheers,
Emmanuel
On Thu, Jun 8, 2017 at 11:32 AM, Joakim Nohlgård
wrote:
> Dear developers,
> Eistec have begun adding support for more Kinetis Freedom
SCH implementation
> in RIOT. Are there any more details available on this project?
>
> Thanks,
> Ken
>
> http://riot-os.org/files/RIOT-Seminar-2017/RIOT-Spring-
> Seminar-Watteyne.pdf
>
> On 04/28/2017 06:26 AM, Emmanuel Baccelli wrote:
>
> Hi everyone,
>
>
Hi Samir,
for this, I suggest you take a look at the companies that have given a talk
at the last RIOT Summit. See:
http://summit.riot-os.org/2017/#speakers and
http://summit.riot-os.org/2017/blog/2017/10/06/slides/
Some examples of products and deployments using RIOT that I have seen
recently
Hi Thomas,
thanks for letting us know! Is there any pointer/URL or preliminary
documentation that is available already concerning this project?
Cheers,
Emmanuel
On Wed, Oct 11, 2017 at 1:57 PM, Thomas C. Schmidt wrote:
> Dear RIOTers,
>
> this is to announce SANE,
Dear RIOTers,
The RIOT Summit 2017 was a success, with talks, break-sessions and lively
interactions for 2 days, with over 100 participants from Europe, North- and
South-America, as well as Asia.
The slides for the presentations of day 1 of the Summit are now available
online at
Hi there,
RIOT supports CCN-lite and NDN stacks, which are both offering ICN
capabilities over low-power wireless networks as demonstrated in [1][2][3]
among others.
For preliminary instructions/tutorial on how to use these stacks see [4]
[5].
The boards supported by RIOT are listed there [6].
Yeehah!
Thanks to everyone involved and to Kaspar for managing this release!
Cheers
Emmanuel
On Fri, May 11, 2018 at 6:09 PM, Kaspar Schleiser
wrote:
> Dear RIOTers,
>
> we are happy to announce the 15th official release of RIOT:
>
> --- * RIOT 2018.0 *
Hi Patrick,
welcome to RIOT!
I'm not the best specialist of the topic, maybe others will have
complementary advice (or may correct me).
Can you scan through the wikipage on this topic [1] ?
For the L4, pm is not there yet.
What you could do is look at [2] an consider extending for L4.
Then if
Yay!! Congrats to all involved parties and thanks Hauke for managing this
release.
Cheers!
Emmanuel
On Oct 27, 2017 12:38 PM, "Hauke Petersen"
wrote:
> Dear RIOTers,
>
> we are happy to announce the 13th official release of RIOT:
>
> --- * RIOT
Indeed, thanks to Sebastian for managing this release, and congrats to all
involved parties!
On Jan 31, 2018 23:55, "Cenk Gündoğan" wrote:
> congratulations to everyone involved!
>
> ... and kudos to Sebastian for managing this release so elegantly (:
>
> Cheers,
> Cenk
1 - 100 of 135 matches
Mail list logo