On 2/9/19 4:11 pm, Sebastian Huber wrote:
> On 02/09/2019 08:00, Chris Johns wrote:
I do not see any upside adding this library or wrapping specific functions
this way.
>>> The benefits are:
>>>
>>> * Slightly more compact (the event indicates the function and the data can
>>> be
>>> u
On 02/09/2019 08:04, Chris Johns wrote:
On 2/9/19 3:58 pm, Sebastian Huber wrote:
Hello,
the
const char *rtems_version_control_key( void )
{
#ifdef RTEMS_VERSION_VC_KEY
return RTEMS_VERSION_VC_KEY;
#else
return NULL;
#endif
}
returns NULL, if no RTEMS_VERSION_VC_KEY is defined, e.g. the
On 02/09/2019 08:00, Chris Johns wrote:
I do not see any upside adding this library or wrapping specific functions
this way.
The benefits are:
* Slightly more compact (the event indicates the function and the data can be
used for the caller address instead, the generic function entry/exit needs
On 2/9/19 3:58 pm, Sebastian Huber wrote:
> Hello,
>
> the
>
> const char *rtems_version_control_key( void )
> {
> #ifdef RTEMS_VERSION_VC_KEY
> return RTEMS_VERSION_VC_KEY;
> #else
> return NULL;
> #endif
> }
>
> returns NULL, if no RTEMS_VERSION_VC_KEY is defined, e.g. the RTEMS sources
>
On 02/09/2019 08:01, Chris Johns wrote:
On 2/9/19 3:42 pm, Sebastian Huber wrote:
On 02/09/2019 07:22, Chris Johns wrote:
The sb-bootstrap command has proved to be useful. The attached rtems-bootsrap is
is a stand alone version that could be added to the top directory of rtems.git.
Should I cre
On 2/9/19 3:42 pm, Sebastian Huber wrote:
> On 02/09/2019 07:22, Chris Johns wrote:
>> The sb-bootstrap command has proved to be useful. The attached
>> rtems-bootsrap is
>> is a stand alone version that could be added to the top directory of
>> rtems.git.
>> Should I create a patch to do this?
>
Hello,
the
const char *rtems_version_control_key( void )
{
#ifdef RTEMS_VERSION_VC_KEY
return RTEMS_VERSION_VC_KEY;
#else
return NULL;
#endif
}
returns NULL, if no RTEMS_VERSION_VC_KEY is defined, e.g. the RTEMS
sources are not managed by Git. Naive users like me may produce a NULL
pointe
On 2/9/19 3:37 pm, Sebastian Huber wrote:
> On 01/09/2019 04:29, Chris Johns wrote:
>> On 30/8/19 11:07 pm, Sebastian Huber wrote:
>>> Introduce new library librtemsrecordwrap.a which contains wrappers for
>>> operating system functions which produce entry/exit events.
>>
>> Why not enhance the tra
On 02/09/2019 07:22, Chris Johns wrote:
The sb-bootstrap command has proved to be useful. The attached rtems-bootsrap is
is a stand alone version that could be added to the top directory of rtems.git.
Should I create a patch to do this?
Yes, this would be great.
--
Sebastian Huber, embedded br
On 01/09/2019 04:29, Chris Johns wrote:
On 30/8/19 11:07 pm, Sebastian Huber wrote:
Introduce new library librtemsrecordwrap.a which contains wrappers for
operating system functions which produce entry/exit events.
Why not enhance the trace linker to handle the recorder you have developed? It
Hi,
The sb-bootstrap command has proved to be useful. The attached rtems-bootsrap is
is a stand alone version that could be added to the top directory of rtems.git.
Should I create a patch to do this?
Chris
#! /usr/bin/env python
#
# RTEMS Tools Project (http://www.rtems.org/)
# Copyright 2013-2
On 2/9/19 3:09 pm, Sebastian Huber wrote:
> On 01/09/2019 04:46, Chris Johns wrote:
>> On 31/8/19 5:29 am, Sebastian Huber wrote:
>>> attached are two patches which convert the rtems-record-lttng client program
>>> from C to C++.
>>
>> Is this a step to a full C++ app?
>
> Yes, it is a step.
Grea
On 01/09/2019 04:46, Chris Johns wrote:
On 31/8/19 5:29 am, Sebastian Huber wrote:
attached are two patches which convert the rtems-record-lttng client program
from C to C++.
Is this a step to a full C++ app?
Yes, it is a step.
The following are some observations about the C++ piece of c
Greetings!
I am new to RTEMS and to open source! I am most interested in contributing
to anything BSP or testing suite related but will do most anything that
needs to be done.
I graduated in Dec. 2018 and got a CS degree but my heart is in EE and CE
stuff. Currently I work for an Aerospace compan
On 31/8/19 4:32 am, Vijay Kumar Banerjee wrote:
> This is required to be able to add the PREFIX path as the include
> path in an lvgl based app.
Pushed. Thanks.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hi,
Thank you for the patch.
Can this please be moved as lvgl/hello? It would allow for other examples to be
added.
We need a test for liblvgl.a. Maybe lvgl/wscript can check and not build if not
found.
On 31/8/19 4:23 am, Vijay Kumar Banerjee wrote:
> ---
> README | 2 +-
> lvg
16 matches
Mail list logo