Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

2019-09-02 Thread Christian Mauderer
On 03/09/2019 01:46, Chris Johns wrote: > On 2/9/19 5:42 pm, Vijay Kumar Banerjee wrote: >> On Mon, Sep 2, 2019 at 4:34 AM Chris Johns > > wrote: >> > +     puts("\nRTEMS I2C TEST\n"); >> > +     exit_code = bbb_register_i2c_0(); >> > +     assert(exit_code ==

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

2019-09-02 Thread Vijay Kumar Banerjee
On Tue, Sep 3, 2019 at 5:15 AM Chris Johns wrote: > On 3/9/19 4:56 am, Vijay Kumar Banerjee wrote: > > > +void > > > +libbsdhelper_start_shell(rtems_task_priority prio) > > > +{ > > > + rtems_status_code sc = rtems_shell_init( > > > +

[PATCH] Add a parallel bootstrap command.

2019-09-02 Thread chrisj
From: Chris Johns --- rtems-bootstrap | 270 1 file changed, 270 insertions(+) create mode 100755 rtems-bootstrap diff --git a/rtems-bootstrap b/rtems-bootstrap new file mode 100755 index 00..9db039aada --- /dev/null +++

Re: devel.rtems.org down?

2019-09-02 Thread groups
Thanks Chris and Amar. Andrei > On 2019-September-02, at 19:04, Chris Johns wrote: > > On 3/9/19 10:48 am, Mr. Andrei Chichak wrote: >> Poking around, I find that devel.rtems.org isn’t >> answering. > > We are suffering a sustained load on Trac that is overloading

Re: [PATCH] Address several issues from compiling examples

2019-09-02 Thread Martin Erik Werner
On Tue, 2019-09-03 at 01:48 +0200, Martin Erik Werner wrote: > Compiling the code from examples "code-block:: c" along with public > includes and a bsp exposed a few issues amongst a lot of false > positives. Address some of these: (...) As per the sent patch, I've had some "fun" trying to run

Re: [PATCH] Address several issues from compiling examples

2019-09-02 Thread Chris Johns
On 3/9/19 9:48 am, Martin Erik Werner wrote: > Compiling the code from examples "code-block:: c" along with public > includes and a bsp exposed a few issues amongst a lot of false > positives. Address some of these: Pushed. Thank you. Chris ___ devel

[PATCH] Address several issues from compiling examples

2019-09-02 Thread Martin Erik Werner
Compiling the code from examples "code-block:: c" along with public includes and a bsp exposed a few issues amongst a lot of false positives. Address some of these: * Terminate struct declarations with ';'. Mainly for pedantic correctness. * Show ptrdiff_t instead of size_t for the sbrk()

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

2019-09-02 Thread Chris Johns
On 3/9/19 4:56 am, Vijay Kumar Banerjee wrote: > > +void > > +libbsdhelper_start_shell(rtems_task_priority prio) > > +{ > > +     rtems_status_code sc = rtems_shell_init( > > +             "SHLL", > > +             STACK_SIZE_SHELL, > > +     

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

2019-09-02 Thread Chris Johns
On 2/9/19 5:42 pm, Vijay Kumar Banerjee wrote: > On Mon, Sep 2, 2019 at 4:34 AM Chris Johns > wrote: > > +     puts("\nRTEMS I2C TEST\n"); > > +     exit_code = bbb_register_i2c_0(); > > +     assert(exit_code == 0); > > Is this needed for the display to

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

2019-09-02 Thread Vijay Kumar Banerjee
> > > +void >> > +libbsdhelper_start_shell(rtems_task_priority prio) >> > +{ >> > + rtems_status_code sc = rtems_shell_init( >> > + "SHLL", >> > + STACK_SIZE_SHELL, >> > + prio, >> > + CONSOLE_DEVICE_NAME, >> > + false, >> > +

Re: [PATCH] Add lvgl_hello: Sample Hello world app using littleVGL and libbsd

2019-09-02 Thread Vijay Kumar Banerjee
On Mon, Sep 2, 2019 at 4:34 AM Chris Johns wrote: > 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. > > OK. Understood.

Re: [PATCH] record: Add wrappers for malloc() functions

2019-09-02 Thread Sebastian Huber
On 02/09/2019 09:00, Chris Johns wrote: Why not generate the call to `rtems_record_produce_2`? You should be able to determine this give you will know there in a single item plus the return address to record. In fact there is little need for `rtems_record_produce_n` if you have [1..n] already

Re: [PATCH] record: Add wrappers for malloc() functions

2019-09-02 Thread Chris Johns
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 >>>

Re: rtems_version_control_key() may return NULL

2019-09-02 Thread Sebastian Huber
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.

Re: [PATCH] record: Add wrappers for malloc() functions

2019-09-02 Thread Sebastian Huber
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

Re: rtems_version_control_key() may return NULL

2019-09-02 Thread Chris Johns
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