Age | Commit message (Collapse) | Author |
|
|
|
This fixes the build for all other BSPs.
|
|
The CFLAGS influence the entire build. Using them for tests is madness. The
funny defines affected the rtems_board_support_package() directive.
|
|
|
|
Import ISVV testsuite from
CSW-RTEMSISVV-2022-TSP-05453_1-rtems-smp-isvv-iva-test-procedures.zip
with an SHA256 hash of
fdbe9ee336fd29da42ea7a0b8de558a369e7b3e0a2009b9a5c500f00fa960b88
|
|
|
|
|
|
|
|
|
|
If the CSafeLoader is available, load only the necessary build items.
This considerably speeds up the build setup time if the CSafeLoader is
used.
|
|
This makes it more obvious that this is an item UID.
|
|
Move the item cache handling to a ItemCache class. Implement this class
depending on the availability of CSafeLoader.
|
|
The CSafeLoader uses the C libyaml libary to considerably speed up the
loading of YAML files.
|
|
|
|
|
|
|
|
Make tests for libdl configurable since they are currently not
reproducible, see #4941.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These memory benchmark programs are not supposed to run. Instead, they
can be analysed on the host system to measure the memory usage of
features. See the membench module of rtems-central.
Update #3716.
|
|
The goal of the RTEMS pre-qualification activity #3701 is a specified
and validated subset of RTEMS. For users of the pre-qualified subset of
RTEMS it is important to not accidentally use not pre-qualified
features. One way to achieve this, is to build only the sources of the
pre-qualified feature set. This customized build is enabled by the new
build configuration option RTEMS_QUAL. If it is enabled, then only the
pre-qualified subset of RTEMS is built and installed.
Building with RTEMS_QUAL enable is currently only supported for the
sparc/leon3 BSP family. To support an RTEMS_QUAL enabled build, changes
in the CPU port and the BSP are required to only use features of the
pre-qualified feature set.
Update #4963.
|
|
Move the RTEMS test printer and rtems_test_exit() to separate files, to
remove dependencies from the begin/end test messsage support.
Update #4963.
|
|
Update #4925.
|
|
This helps to validate that the data was transferred correctly.
|
|
Close #4971.
|
|
This can be used to report that nested test cases did run in a test
case.
Update #4971.
|
|
The pinctrl-0 of the video_mux might overwrite pin settings done by
other peripherals. Disabling it by default prevents unexpected pin
settings.
|
|
With this, it is possible to use GPIOs as CS pins in the LPSPI. To avoid
additional complexity, the GPIOs will have the same limitations as the
native (hardware) CS pins.
The GPIO CS feature adds a number of extra code when starting SPI
transfers on this controller. Therefore it is possible to disable the
additional code by just setting the IMXRT_LPSPI_MAX_CS option to 0. In
that case only native CS pins are supported.
At the moment, this feature is only enabled on i.MXRT1166 by default
because it is not tested on i.MXRT1050. But it should work there too.
|
|
Device trees allow mixing different kinds of GPIOs in one property. For
that it is usefull to only provide a pointer to an arbitrary location in
the property and initialize a GPIO from that.
|
|
Update #3716.
|
|
For uniprocessor configurations, the selection of
RTEMS_MULTIPROCESSOR_RESOURCE_SHARING results in a priority ceiling
mutex.
Build the MrsP validation tests only if RTEMS_SMP is enabled.
Update #3716.
|
|
Updates #4968
|
|
|
|
|
|
This imports the TTC hardware definitions for the triple timer counters
on various Xilinx platforms. This was imported as specified in the
VERSION file in this commit.
|
|
|
|
Update #3716.
|
|
The goal is to get code and branch coverage from actual tests and not
the test support itself.
|
|
|
|
The code coverage build is usually done without compiler optimizations.
This results in long performance test runtimes and useless performance
results.
|
|
Test some compiler builtins which may use integer library routines:
https://gcc.gnu.org/onlinedocs/gccint/Integer-library-routines.html
Update #3716.
|
|
|
|
Enable an individual testsuite only through the corresponding enable.
Use BUILD_TESTS to change the default value of the individual testsuite
enable options. This allows the user to enable all testsuites with
specific exceptions.
For example, this builds all testsuites except the benchmarks:
[arch/bsp]
BUILD_TESTS = True
BUILD_BENCHMARKS = False
|
|
Change the public image data type to a void pointer.
|