GSOC 2017 Approaching

Kevin Du Huanpeng norep1y at
Tue Jan 10 23:12:21 UTC 2017


------------------ Original ------------------
From: Chris Johns <chrisj at>
Date: 周三,1月 11,2017 08:01
To: Denis Obrezkov <denisobrezkov at>, joel <joel at>
Cc: rtems-users at <users at>
Subject: Re: GSOC 2017 Approaching

On 10/01/2017 19:46, Denis Obrezkov wrote:
> I am a first-year phd student in Russia and I can help you to recruit me:)

Welcome and thank you for presenting these idea.

I have trimmed the list to the ideas I have answered ...

> Secondly, some degree of IoT support is very desirable, because nowadays
> IoT
> lacks reliability and safety. Thus, I think, this task includes not only
> porting packages
> and implementing protocols but also architecture development and creation of
> documentation that describes how 
> Lastly, I think it would be good to implement some kind of configuration
> tool support.
> As example, Linux has a very simple but also very flexible configuration
> tool..
I was working on porting kbuild to rtems.  Most source code can be compile by kbuild.  Do you interested in continue my work?

This is something RTEMS needs. There are 2 parts to configuring RTEMS 
for an application:

1. Kernel build
2. Runtime configuration

A kernel configuration tool will need to wait until we change from the 
autotconf/automake build system to waf. Part of the requirements for waf 
is to bring all the configuration items in RTEMS, including the BSP 
options, out into a formalised interface with suitable documentation. 
Until this is done and we have something concrete any attempts at a 
configuration could be wasted effort. The ability to get this 
information from the current build system is difficult and messy.

The runtime configuration would be based around confdefs.h and it would 
generate an init.c or system.h or whatever. This is open but I am not 
sure how big or challenging a task it is on it's own.

users mailing list
users at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list