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] https://siliconlabs.github.io/Gecko_SDK_Doc/ezr32lg/html/ezradio__comm_8c.html On Thu, Dec 8, 2016 at 10:56 AM, Hauke Petersen <hauke.peter...@fu-berlin.de > wrote: > Hi again, > > On 08.12.2016 10:49, Akshay Mishra wrote: > > I have located the track. Now the license question -- > > Is it ok to use bits of code from the Silicon Labs driver here ( > https://siliconlabs.github.io/Gecko_SDK_Doc/ezr32lg/html/ez > radio__comm_8c_source.html) as per RIOT-OS licensing norms ? > > In general yes, but it depends which license SiLabs has put on the code, > so as long as it is compatible to LGPL you could use it. But if that is the > most elegant solution is something of personal taste... :-) > > Cheers, > Hauke > > > > > On 8 December 2016 at 14:58, Akshay Mishra <aks...@dspworks.in> wrote: > >> 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 only modifying the WG to LG which changes it from Cortex-M4 >> to Cortex-M3. >> >> *Akshay Mishra* >> >> On 8 December 2016 at 14:31, Martine Lenders < <m...@martine-lenders.eu> >> m...@martine-lenders.eu> wrote: >> >>> 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 Mishra <aks...@dspworks.in>: >>> > Hello, >>> > I tried it on the SLWSTK6220a with the EZR32LG. While I was >>> able to >>> > get riot-os working on it, the ipv6 address does not get assigned. >>> > >>> > How does the interface get enabled ? I did not enable any tap on the >>> host. >>> > >>> > Thanks, >>> > Akshay >>> > >>> > >>> > _______________________________________________ >>> > devel mailing list >>> > devel@riot-os.org >>> > https://lists.riot-os.org/mailman/listinfo/devel >>> > >>> _______________________________________________ >>> devel mailing list >>> devel@riot-os.org >>> https://lists.riot-os.org/mailman/listinfo/devel >>> >> >> > > > _______________________________________________ > devel mailing > listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > >
_______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
