Re: [riot-devel] wolfSSL port to RIOT OS

Hi Larry, Hi Kaleb great! I did not see any pull-request yet to RIOT's master branch? Can we expect one soonish? Cheers Emmanuel On Fri, Dec 9, 2016 at 1:41 AM, la...@wolfssl.com wrote: > Kaleb, > > Can you write up a blog post to let our community know that this is >

[riot-devel] Raspberry & 6LoWPAN HowTo outdated

Hi, does someone plan to update following HowTo: https://github.com/RIOT-OS/RIOT/wiki/How-to-install-6LoWPAN-Linux-Kernel-on-Raspberry-Pi I have all is needed: - OpenLabs Raspberry Pi 802.15.4 radio - Raspberry Pi 2 or Raspberry Pi 3 - Atmel SAM R21 Xplained Pro but still fail to do

Re: [riot-devel] wolfSSL port to RIOT OS

Hi Emmanuel, I am building on Mac OS X initially. Everything is working great. I have three examples that build and run with RIOT_OS. A benchmark application, a cryptographic test application and a TLS client/server + cryptographic test application. These three example applications demonstrate

Re: [riot-devel] SiLabs Gecko

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]

Re: [riot-devel] SiLabs Gecko

Hello Bas, I checked against EFM2RIOT. EZR32LG works with it also like a charm. Also the siliconlabs driver rely on peripherals which you do seem to have covered. the efm32_common covers the peripherals. thanks, On 8 December 2016 at 15:37, Bas Stottelaar wrote: > Hi

Re: [riot-devel] SiLabs Gecko

Hi Akshay, Somewhat related, but I have been working on EFM32 support for RIOT-OS in the past year. You can find my work (in progress) at [1]. A PR for one specific board (Thunderboard Sense) is at [2]. Chances are that [3] relies on the use of 'emlib'. In that case, I would strongly suggest to

Re: [riot-devel] SiLabs Gecko

Hi Akshay, if I understand it correctly, you use the ezr32lg? So I would suggest you start by porting that CPU first: - create the `ezr32lg` cpu - create a `ezr32_common` folder - move everything from the `ezr32wg` to the common folder that can be re-used (I would suppose this includes all

Re: [riot-devel] SiLabs Gecko

Thanks Martine, It is possible that there is no RF support (I thought so but was not sure.). I can look at porting it if there can be pointers. The example used was gnrc_networking on the latest git clone. One confession, :-|, is that the EZR32WG is supported and I worked on the basic examples

Re: [riot-devel] SiLabs Gecko

Hi Akshay, I fear you have to be a bit more specific than that. What application are you using e.g., which network stack? Also, I might be mistaking but it seems like there is no RF support for the EZR32LG in master yet. Maybe that is the problem? Cheers, Martine 2016-12-08 8:34 GMT+01:00 Akshay