Description of rtems-libbsd testsuite applications

Hello, is there already somewhere a file which gives some short description what the different test applications in the testsuite directory (are supposed to) do? If not, would you accept patches with some short descriptions and maybe an example output? Cheers, Jan Deutsches Zentrum für Luf

Re: Description of rtems-libbsd testsuite applications

Hello Jan, On 14/02/2020 09:46, jan.som...@dlr.de wrote: > Hello, > > is there already somewhere a file which gives some short description what the > different test applications in the testsuite directory (are supposed to) do? None that I know of. > If not, would you accept patches with some s

Re: Description of rtems-libbsd testsuite applications

Hello Jan, On 14/02/2020 09:46, jan.som...@dlr.de wrote: is there already somewhere a file which gives some short description what the different test applications in the testsuite directory (are supposed to) do? If not, would you accept patches with some short descriptions and maybe an example

[PATCH 3/4] rtems: Simplify _RTEMS_tasks_Initialize_user_task()

Due to the system initialization order, the _Thread_Global_constructor must be 0 in this function. --- cpukit/rtems/src/taskinitusers.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/cpukit/rtems/src/taskinitusers.c b/cpukit/rtems/src/taskinitusers.c index a4f948afc9..1f9

[PATCH 1/4] config: Remove CONFIGURE_HAS_OWN_INIT_TASK_TABLE

The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_* configuration options. These two options are probably unused, see also: * https://lists.rtems.org/pipermail/users/2019-April/033129.html * https://lists.rtems.org/pipermail/users/2019

[PATCH 2/4] config: Simplify initialization task config

With the removal of the CONFIGURE_HAS_OWN_INIT_TASK_TABLE configuration option at most one Classic API user initialization task can be configured. Provide an RTEMS API configuration table for backward compatibility. Update #3873. --- cpukit/Makefile.am | 2 + cpukit/include

[PATCH 4/4] config: Bring back RTEMS 4.11 configuration table

This improves API backward compatibility of RTEMS 5.1 to previous versions. --- cpukit/include/rtems/rtems/config.h | 61 +++ cpukit/rtems/src/getapiconfig.c | 18 +++ testsuites/sptests/spsysinit01/init.c | 21 3 files changed, 100 inse

Re: [PATCH] testsuite/newlib: Check newlib does not touch an assigned std FILE pointer

On 2020-02-14 17:11, Sebastian Huber wrote: On 14/02/2020 04:41, chr...@rtems.org wrote: From: Chris Johns Update #3870 ---   testsuites/libtests/newlib01/init.c | 16 +++-   1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/testsuites/libtests/newlib01/init.c b/test

Re: [PATCH] tester: Add qemu_opts_serial

On 2020-02-14 17:03, Sebastian Huber wrote: On 14/02/2020 04:00, Chris Johns wrote: I must be must be mising what has changed. I cannot see the "wrong options that have changed? I removed the serial/monitor settings from qemu_opts_base and moved them to the new qemu_opts_serial. The realvi

AW: Description of rtems-libbsd testsuite applications

Thanks for the suggestions. I have to figure out what some of the tests do anyway and writing it down somewhere will also prevent future-me to do it again. If I have some notes, is it ok to prepare a README.md inside the individual test's directory or do you prefer a single README inside the test

Re: AW: Description of rtems-libbsd testsuite applications

On 14/02/2020 11:30, jan.som...@dlr.de wrote: Thanks for the suggestions. I have to figure out what some of the tests do anyway and writing it down somewhere will also prevent future-me to do it again. If I have some notes, is it ok to prepare a README.md inside the individual test's directory

[PATCH] posix: Remove

This file contained duplicate prototypes for standard POSIX functions declared in . --- cpukit/headers.am | 1 - cpukit/include/rtems/posix/ptimer.h | 88 - cpukit/posix/src/timersettime.c | 1 - 3 files changed, 90 deletions(-) delete m

[PATCH] config: Remove CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE

The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_* configuration options. These two options are probably unused, see also: * https://lists.rtems.org/pipermail/users/2019-April/033129.html * https://lists.rtems.org/pipermail/users/2019-Apr

rtems-examples hello no output devfs

Hi I haven't investigated or checked on other bsps but the xilinx qemu bsp has no output with the hello world in examples. It uses the devfs. Changing it to the default filesystem results in it working. I am suspicious of something with all the termios and new console changes breaking it. --joel

Re: rtems-examples hello no output devfs

On 14/02/2020 13:57, Joel Sherrill wrote: Hi I haven't investigated or checked on other bsps but the xilinx qemu bsp has no output with the hello world in examples. It uses the devfs. Changing it to the default filesystem results in it working. I am suspicious of something with all the term

Remove support for RTEMS_SCHEDSIM?

Hello, there is a RTEMS_SCHEDSIM define which is used in a couple of files: ./cpukit/include/rtems/confdefs.h:#ifdef RTEMS_SCHEDSIM ./cpukit/include/rtems/confdefs.h:#ifndef RTEMS_SCHEDSIM ./cpukit/include/rtems/confdefs.h:#ifndef RTEMS_SCHEDSIM ./cpukit/include/rtems/confdefs.h:#ifndef RTEMS_SC

Re: Remove support for RTEMS_SCHEDSIM?

On 14/02/2020 15:31, Sebastian Huber wrote: The problem with this define is that it cannot within RTEMS. The problem with this define is that it cannot be tested within RTEMS. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listi

Re: Remove support for RTEMS_SCHEDSIM?

I guess it is time to kill it. On Fri, Feb 14, 2020 at 8:36 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/02/2020 15:31, Sebastian Huber wrote: > > > The problem with this define is that it cannot within RTEMS. > The problem with this define is that it cannot be tested w

Re: rtems-examples hello no output devfs

On Fri, Feb 14, 2020 at 7:08 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/02/2020 13:57, Joel Sherrill wrote: > > > Hi > > > > I haven't investigated or checked on other bsps but the xilinx qemu > > bsp has no output with the hello world in examples. It uses the devfs. >

Re: Remove support for RTEMS_SCHEDSIM?

On 14/02/2020 15:42, Joel Sherrill wrote: I guess it is time to kill it. I already have a smoking gun in my hands. I think it would be possible to make it working again with some effort. However, it is quite easy to add scheduler test scenarios in the RTEMS test suite itself, for example:

Re: rtems-examples hello no output devfs

On 14/02/2020 15:45, Joel Sherrill wrote: On Fri, Feb 14, 2020 at 7:08 AM Sebastian Huber > wrote: On 14/02/2020 13:57, Joel Sherrill wrote: > Hi > > I haven't investigated or checked on other bsps but the xilinx qemu > bsp has no

Re: rtems-examples hello no output devfs

On Fri, Feb 14, 2020 at 9:16 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/02/2020 15:45, Joel Sherrill wrote: > > On Fri, Feb 14, 2020 at 7:08 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 14/02/2020 13:57, Joel Sherrill wrote: >> >> > Hi >> >

Re: Remove support for RTEMS_SCHEDSIM?

On Fri, Feb 14, 2020 at 9:04 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/02/2020 15:42, Joel Sherrill wrote: > > > I guess it is time to kill it. > > I already have a smoking gun in my hands. I think it would be possible > to make it working again with some effort. Howe

Re: rtems-examples hello no output devfs

On 14/02/2020 16:29, Joel Sherrill wrote: On Fri, Feb 14, 2020 at 9:16 AM Sebastian Huber > wrote: On 14/02/2020 15:45, Joel Sherrill wrote: On Fri, Feb 14, 2020 at 7:08 AM Sebastian Huber mailto:sebastian.hu...@embedded-brains.de>> w

Re: Remove support for RTEMS_SCHEDSIM?

On 14/02/2020 16:31, Joel Sherrill wrote: On Fri, Feb 14, 2020 at 9:04 AM Sebastian Huber > wrote: On 14/02/2020 15:42, Joel Sherrill wrote: > I guess it is time to kill it. I already have a smoking gun in my hands. I think it would b

Re: Remove support for RTEMS_SCHEDSIM?

On Fri, Feb 14, 2020 at 9:42 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/02/2020 16:31, Joel Sherrill wrote: > > > > On Fri, Feb 14, 2020 at 9:04 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 14/02/2020 15:42, Joel Sherrill wrote: >> >> > I g

[PATCH 12/18] config: Add _Thread_Idle_stack_size

Move the idle thread stack size configuration constant out of the configuration table. Add THREAD_IDLE_STACK_SIZE_DEFAULT and use it to provide a default definition of the idle thread stack size constant. Update #3875. --- cpukit/Makefile.am| 1 + cpukit/headers.am

[PATCH 11/18] config: Add _Watchdog_Ticks_per_timeslice

Move the ticks per timeslice configuration constant out of the configuration table. Add WATCHDOG_TICKS_PER_TIMESLICE_DEFAULT and use it to provide a default definition of the watchdog ticks per timeslice constant. Update #3875. --- cpukit/Makefile.am | 1 + cpukit/inclu

[PATCH 17/18] config: Add _SMP_Is_enabled

Move the is SMP enabled configuration constant out of the configuration table. Since this was the last configuration constant in rtems_configuration_table, remove this type. Update #3875. --- cpukit/include/rtems/confdefs.h | 14 -- cpukit/include/rtems/config.h| 31 ++--

[PATCH 01/18] Remove rtems_configuration_get_posix_api_configuration()

The corresponding data structure not longer exists. This function was not tested and documented. Close #3871. --- cpukit/include/rtems/config.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/cpukit/include/rtems/config.h b/cpukit/include/rtems/config.h index c1d735f587..1c9b35da87 100644 -

[PATCH 08/18] posix: Remove

This file contained duplicate prototypes for standard POSIX functions declared in . --- cpukit/headers.am | 1 - cpukit/include/rtems/posix/ptimer.h | 88 - cpukit/posix/src/timersettime.c | 1 - 3 files changed, 90 deletions(-) delete m

fopen() on /dev/console

Hi I was porting some code from Linux to RTEMS. It doesn't use stdin/out, error directly but does all debug IO to a configured file. Most of the time when running on Linux, the device is /dev/stderr. For the RTEMS port, I added link(/dev/console, /dev/stderr) to the init task and that worked. But

[PATCH 16/18] config: Add _SMP_Processor_configure_maximum

Move the processor maximum configuration constant out of the configuration table. Update #3875. --- cpukit/include/rtems/confdefs.h | 12 +++- cpukit/include/rtems/config.h| 14 +++--- cpukit/include/rtems/score/smp.h | 13 + 3 files changed, 23 insertions(+), 16

[PATCH 18/18] config: Add

Unify handling of obsolete configuration options. Change license to BSD-2-Clause. Update #3053. Update #3875. --- cpukit/header-dirs.am| 2 + cpukit/headers.am| 1 + cpukit/include/rtems/confdefs.h | 156 +--- cpukit/in

[PATCH 06/18] rtems: Simplify _RTEMS_tasks_Initialize_user_task()

Due to the system initialization order, the _Thread_Global_constructor must be 0 in this function. --- cpukit/rtems/src/taskinitusers.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/cpukit/rtems/src/taskinitusers.c b/cpukit/rtems/src/taskinitusers.c index 0645de324a..3f9

[PATCH 00/18] Start with splitting up confdefs.h

This is the first round of patches to split up confdefs.h. See also: https://devel.rtems.org/ticket/3875 Sebastian Huber (18): Remove rtems_configuration_get_posix_api_configuration() config: Remove unused configuration constant monitor: Use proper API for all config constants config: Re

[PATCH 07/18] config: Bring back RTEMS 4.11 configuration table

This improves API backward compatibility of RTEMS 5.1 to previous versions. --- cpukit/include/rtems/rtems/config.h | 61 +++ cpukit/rtems/src/getapiconfig.c | 18 +++ testsuites/sptests/spsysinit01/init.c | 21 3 files changed, 100 inse

[PATCH 13/18] config: Add _Thread_Idle_body

Move the idle thread body configuration constant out of the configuration table. Provide a default definition of the idle thread body constant. Update #3875. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/confdefs.h | 7 +++--- cpukit/include/rtems/conf

[PATCH 14/18] config: Add _Workspace_Size

Move the workspace size configuration constant out of the configuration table. Update #3875. --- cpukit/headers.am| 1 + cpukit/include/rtems/confdefs.h | 3 +- cpukit/include/rtems/config.h| 8 +--- cpukit/include/rtems/score/wkspacedata.h | 65 +++

[PATCH 04/18] config: Remove CONFIGURE_HAS_OWN_INIT_TASK_TABLE

The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_* configuration options. These two options are probably unused, see also: * https://lists.rtems.org/pipermail/users/2019-April/033129.html * https://lists.rtems.org/pipermail/users/2019

[PATCH 05/18] config: Simplify initialization task config

With the removal of the CONFIGURE_HAS_OWN_INIT_TASK_TABLE configuration option at most one Classic API user initialization task can be configured. Provide an RTEMS API configuration table for backward compatibility. Update #3873. --- cpukit/Makefile.am | 2 + cpukit/include

[PATCH 10/18] config: Add _Watchdog_Microseconds_per_tick

Move the microseconds per tick configuration constant out of the configuration table. Add WATCHDOG_MICROSECONDS_PER_TICK_DEFAULT and use it to provide a default definition of the watchdog ticks constants. Update #3875. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/c

[PATCH 15/18] config: Add _Workspace_Is_unified

Move the unified workspace configuration constant out of the configuration table. Provide a default definition of the unified workspace constant. Update #3875. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/confdefs.h| 9 cpukit/include/rtems/co

[PATCH 09/18] config: Remove CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE

The CONFIGURE_HAS_OWN_INIT_TASK_TABLE and CONFIGURE_POSIX_HAS_OWN_INIT_THREAD_TABLE are the last *_HAS_OWN_* configuration options. These two options are probably unused, see also: * https://lists.rtems.org/pipermail/users/2019-April/033129.html * https://lists.rtems.org/pipermail/users/2019-Apr

[PATCH 03/18] monitor: Use proper API for all config constants

--- cpukit/libmisc/monitor/mon-config.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/cpukit/libmisc/monitor/mon-config.c b/cpukit/libmisc/monitor/mon-config.c index 852e780d04..95b7798173 100644 --- a/cpukit/libmisc/monitor/mon-config.c +++ b/cpukit/libmisc/moni

[PATCH 02/18] config: Remove unused configuration constant

--- cpukit/include/rtems/confdefs.h | 1 - cpukit/include/rtems/config.h | 10 -- 2 files changed, 11 deletions(-) diff --git a/cpukit/include/rtems/confdefs.h b/cpukit/include/rtems/confdefs.h index f39172cffb..137a9edb5c 100644 --- a/cpukit/include/rtems/confdefs.h +++ b/cpukit/inclu

Re: fopen() on /dev/console

On 14/02/2020 17:02, Joel Sherrill wrote: Hi I was porting some code from Linux to RTEMS. It doesn't use stdin/out, error directly but does all debug IO to a configured file. Most of the time when running on Linux, the device is /dev/stderr. For the RTEMS port, I added link(/dev/console, /dev

Multicast on libbsd and Qemu

Hi I am trying to bring up the FACE example application on RTEMS. I am using the Zyng BSP on Qemu. I need some configuration advice on multicast both on how to configure libbsd and qemu. The application has multiple components running on the Zynq which communicate via multicast UDP and some of tha

Re: fopen() on /dev/console

On Fri, Feb 14, 2020 at 10:11 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 14/02/2020 17:02, Joel Sherrill wrote: > > > Hi > > > > I was porting some code from Linux to RTEMS. It doesn't use stdin/out, > > error directly but does all debug IO to a configured file. Most of t

[PATCH] libio: Add POSIX user environment to TCB

The IO library used a POSIX key to store an optional POSIX user environment pointer. This pulled in the POSIX keys support in every application configuration. Add a user environment pointer to the thread control block (TCB) instead. Applications which do not need the POSIX user environment will

Re: [PATCH 18/18] config: Add

Hi Sebastian, This makes sense. Is there any reason for the ordering? If possible, I think grouping by obsoleted version or alphabetical ordering would be a good idea. On Fri, Feb 14, 2020 at 9:03 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Unify handling of obsolete confi

[PATCH] first commit

--- testsuites/samples/hello/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/init.c index 34ded37c55..7f165d17a5 100644 --- a/testsuites/samples/hello/init.c +++ b/testsuites/samples/hello/init.c @@ -22,7 +22,7 @

Re: [PATCH] first commit

Hello I am Suyash Singh and this is my first commit. I am from India and currently in 2nd year of BTech Computer Science Engineering. I am hoping to participate in RTEMS as a GSOC student and beyond. On Sat, Feb 15, 2020 at 12:56 PM suyash singh wrote: > --- > testsuites/samples/hello/init.c