| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Use rtems_shell_wait_for_input() similar to other potentially
interactive test programs.
|
|
|
|
| |
A device tree blob must be aligned on an 8-byte boundary.
|
|
|
|
| |
A device tree blob must be aligned on an 8-byte boundary.
|
|
|
|
|
| |
Use the stack pointer to check if we have to return the real device tree
since bsp_fdt_get() may get called before the BSS is cleared to zero.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RTEMS untar implementation had problems with overwriting or integrating
archives into existing directory structures. This patch adapts the
behavior to mimic that of a GNU tar or BSD tar and extends the tar01
test to check for the behavior. That is:
* If a directory structure exists, the files from the archive will be
integrated. Existing files are overwritten.
* If a file exists and the archive contains a directory with the same
name, the file is removed and a directory is created. In the above
example: if l1/l2 is a file it will be overwritten with a new
directory.
* If a directory exists and the archive contains a file with the same
name, the directory will be replaced if it is empty. If it contains
files, the result is an error.
* An archive also can contain only a file without the parent
directories. If in that case one of the parent directories exists as a
file extracting the archive results in an error. In the example: if
l1/l2 is a file and the archive doesn't contain the directories but
only the file l1/l2/x.txt that would be an error.
* In case of an error, it is possible that the archive has been
partially extracted.
Closes #4568
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The BSPs provide memory for the separate C Program Heap initialization
via _Memory_Get(). Most BSPs provide exactly one memory area. Only two
BSPs provide more than one memory area (arm/altera-cyclone-v and
bsps/powerpc/mpc55xxevb). Only if more than one memory area is
provided, there is a need to use _Heap_Extend(). Provide two
implementations to initialize the separate C Program Heap and let the
BSP select one of the implementations based on the number of provided
memory areas. This gets rid of a dependency on _Heap_Extend(). It
also avoids dead code sections for most BSPs.
Change licence to BSD-2-Clause according to file history.
Update #3053.
|
| |
|
|
|
|
|
|
|
|
| |
This fix came from Code Inspector, flagged by one of the analysis that
was done.
This test code is compiled only but better to address the issues so
future static analysis reports will not include it.
|
|
|
|
|
| |
Close #3250.
Close #4081.
|
|
|
|
|
|
|
| |
This adds the possibility to open an I2C bus with O_NONBLOCK (or set it
later via fcntl) to get non-blocking transmissions. This means that if
the bus is busy, a read, write or transfer ioctl will return with a
EAGAIN errno.
|
|
|
|
|
| |
telnetd01 test cannot be run without a network stack, so this test is being
moved to the rtems-net-legacy repository.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In POSIX, zero size memory allocations are implementation-defined
behaviour. The implementation has two options:
https://pubs.opengroup.org/onlinepubs/9699919799/functions/malloc.html
https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_memalign.html
Linux and FreeBSD return a unique pointer for zero size memory
allocations. Return NULL on RTEMS to more likely catch the use of a
zero size memory area by erroneous applications.
Update #4390.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The zero size allocations had no consistent behaviour in RTEMS. For
example, malloc( 0 ) returned NULL and posix_memalign( &p, align, 0 )
returned in p a unique pointer (or NULL if no memory is available). In
POSIX, zero size memory allocations are implementation-defined
behaviour. The implementation has two options:
https://pubs.opengroup.org/onlinepubs/9699919799/functions/malloc.html
https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_memalign.html
Linux and FreeBSD return a unique pointer for zero size memory
allocations. Use this approach for RTEMS as well throughout the memory
allocation directives
Close #4390.
|
|
|
|
| |
Flexible array members must not appear in the middle of a structure.
|
| |
|
|
|
|
|
|
|
| |
The multiplication to calculate the length of the memory area to
allocate may overflow. Return NULL in case of an overflow.
Close #4389.
|
|
|
|
| |
This reverts commit 3299dda2454a8847c670a732f6c12ef1f2cc5dd0.
|
|
|
|
| |
Update #3850
|
|
|
|
| |
Update #3850
|
|
|
|
| |
Update #3850
|
|
|
|
|
|
|
|
|
| |
Fix warning:
testsuites/libtests/block14/init.c:198:8: warning: 'sc' may be used
uninitialized in this function [-Wmaybe-uninitialized]
Update #3689.
|
| |
|
|
|
|
|
|
|
|
| |
Adds a peek function that allows (for example) a file system to suggest
the next blocks that should be used for read ahead. This can increase
the read speed of fragmented files.
Update #3689
|
| |
|
|
|
|
| |
Update #4267.
|
|
|
|
|
| |
This commit adds a basic test that tests all the implemented
RTEMS OFW functions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix a compiler warning about a missing prototype.
If you wonder why the function name is not `static`:
The code in the file only serves a test where the dynamic object loader
(aka dlopen()) should handle duplicated symbols in an archive.
testsuites/libtests/dl10/dl10-o6.c:14:5: warning: no previous prototype
for 'rtems_main_o5' [-Wmissing-prototypes]
14 | int rtems_main_o5 (void)
| ^~~~~~~~~~~~~
|
| |
|
| |
|
| |
|
|
|
|
| |
Close #4034.
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
|
|
|
|
| |
Normally, the expected test step must be a compile time constant. Allow
variable expected test steps for the T_step() and T_assert_step(). This
can be used for parameterized test loops with individual fixtures.
Remove the ability to use custom failure messages due to some
implementation constraints.
Update #3199.
|
|
|
|
|
|
| |
Support a new test plan for each nested fixture.
Update #3199.
|
|
|
|
|
|
|
| |
Return the produced character count. There is no need for a NUL
termination.
Update #3199.
|
| |
|
|
|
|
|
|
|
|
| |
Add support to record thread switch events. This can be used to check
that a blocking operation results in the expected sequence of thread
switches.
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
| |
This macro magic is in line with C11 and C++11, but limits the maximum
count of arguments.
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
| |
Update #3199.
|
|
|
|
|
|
|
|
| |
Rename this header file to later move <t.h> to <rtems/test.h>. The main
feature provided by <rtems/test-info.h> is the output of standard test
information which is consumed by the RTEMS Tester.
Update #3199.
|
|
|
|
| |
Update #3968.
|
|
|
|
|
|
|
| |
Do not generate the test tar archive on the host computer since not all
file systems support symbolic links.
Close #3968.
|
| |
|
|
|
|
| |
Closes #3969
|
|
|
|
| |
Update #2962.
|