[riot-devel] General configuration Task Force

Ken Bannister kb2ma at runbox.com
Mon Jul 9 16:38:14 CEST 2018


+1! I have a to-do to document such parameters for CoAP. This kind of 
tool could provide a systematic and easily repeatable way to share and 
use that information.

Ken


On 07/09/2018 02:41 AM, Martine Lenders wrote:
> Hi,
>
> count me in as well!
>
> Cheers,
> Martine
>
> Am Mo., 9. Juli 2018 um 11:04 Uhr schrieb Francisco Acosta 
> <francisco.acosta at inria.fr <mailto:francisco.acosta at inria.fr>>:
>
>     +1 I'm in!
>
>     On 9 July 2018 10:16:10 CEST, Koen Zandberg <koen at bergzand.net
>     <mailto:koen at bergzand.net>> wrote:
>     >Hi,
>     >
>     >Sounds fun, count me in!
>     >
>     >Koen
>     >
>     >
>     >On 07/09/2018 10:09 AM, Jose wrote:
>     >> Dear maintainers,
>     >>
>     >>
>     >> Last Friday we had an offline discussion with some RIOT people
>     about
>     >> he lack of a mechanism to configure Kernel parameters as well as
>     >> application specific configurations (private keys, timer values,
>     >etc).
>     >> Although RIOT is configurable via CFLAGS, there's no way to
>     (easily)
>     >> expose all configurations and tweak RIOT in a centralized
>     manner. As
>     >> shown, other OS are using several strategies in order to accomplish
>     >> this (KConfig, header files, etc).
>     >>
>     >>
>     >> I want to propose a "Kernel and Application specific configuration"
>     >> Task Force to address these issues. What are your feelings about
>     >this?
>     >> Anyone (besides me) is interested to work in this topic?
>     >>
>     >>
>     >> Cheers,
>     >>
>     >> José
>     >>
>     >> _______________________________________________
>     >> devel mailing list
>     >> devel at riot-os.org <mailto:devel at riot-os.org>
>     >> https://lists.riot-os.org/mailman/listinfo/devel
>
>     -- 
>     Francisco Javier Acosta Padilla
>     Research Engineer at INFINE team
>     Inria Saclay Ile-de-France
>     _______________________________________________
>     devel mailing list
>     devel at riot-os.org <mailto:devel at riot-os.org>
>     https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20180709/50d03b1e/attachment.html>


More information about the devel mailing list