| Commit message (Collapse) | Author | Files | Lines |
|---|
|
Somehow the constraints for CONFIGURE_TICKS_PER_TIMESLICE and
CONFIGURE_EXTRA_MPCI_RECEIVE_SERVER_STACK got mixed up.
Update #4986.
|
|
The processor mask implementation uses flsl() from <strings.h> which is
only BSD visible. Move the implementation to a separate header file to
hide it from the API level. This fixes build errors with GCC 14.
|
|
|
|
The parameters are unused due to API constraints. The functions are
used through function pointers. Alternative implementations may use the
parameters.
Update #4862.
|
|
Unconditionally make a CONFIGURE_TICKS_PER_TIMESLICE value less than or equal
to zero an error.
Update #4986.
|
|
This fixes:
heap.c:268:3: warning: implicit declaration of function 'memset'
|
|
The use of this function is optional. Newer BSPs do not use it.
|
|
Gate CONFIGURE_TICKS_PER_TIMESLICE appropriately behind
CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER.
|
|
When unmounting a JFFS2 filesystem, any outstanding write buffers must
be flushed to disk. In some circumstances, these write buffers are
instantiated by a garbage collection pass and as such no inode number is
associated with it. Due to the way that JFFS2 processes these garbage
collection passes, a write buffer without any associated inodes will not
be flushed unless it is forced with jffs2_flush_wbuf_pad().
|
|
|
|
This unused variable causes a warning. It is never set or used.
|
|
Prefer macros with a proper namespace.
|
|
On JFFS2 file systems on NOR flash or dataflash that does not have spare
area for metadata and thus does not invoke delayed writes, it is
possible to put the file system into a state where all blocks have been
written to and all files have been deleted from the filesystem. There is
a bug in the JFFS2 file system scan routine that detects this situation
as a corrupted file system since the scan routine relies on "used" space
to discriminate a valid file system when there are blocks that need to
be erased. The correct fix would require a partial rewrite of the scan
routine, so instead this patch tracks the space marked as obsolete along
with space at the end of each block that is otherwise too small to
contain a JFFS2 node so that it can me compared with the dirty space.
Corrupted data (or otherwise non-JFFS2 blocks) will still cause this
check to fail as corrupted data isn't recognized as obsoleted (deleted)
nodes.
|
|
Make sure there is no spurious empty line between the gcov info and the
*** END OF GCOV INFO BASE64 ***
line. This helps to recalculate the hash correctly at the consumer
side.
|
|
|
|
|
|
|
|
This makes them reusable. Change the character type to uint8_t.
|
|
|
|
When the switch to waf occurred, the SMP support in i386 was left out
causing it to accumulate a minor amount of cruft. This enables SMP for
the i386 BSPs that support it and updates them for the API drift that
has occurred since the change.
|
|
|
|
This is already in the error path.
|
|
|
|
This alters the API for rtems_cache_coherent_add_area to allow reporting
of failures that can occur during the process of adding a new area to
the coherent cache heap.
|
|
|
|
Cast getpid() before shifting to avoid truncation of upper bits before
the 64bit XOR occurs.
|
|
|
|
The tmp_fat_fd variable is unconditionally opened in the branch where it
is used within the loop and so must be closed or else risk a resource
leak.
|
|
Change extend_count to uint32_t from uint16_t to avoid a possible
premature integer overflow when it is later used for multiplication.
|
|
|
|
|
|
Updates #4981
|
|
Updates #4981
|
|
Updates #4981
|
|
This cleans up outputUsesInterrupts usage with rtems_termios_device_mode
enum values. The outputUsesInterrupts member was typed as an int, named
as if it were a boolean value, and used as if it were a
rtems_termios_device_mode enum. In this patch, values assigned to
outputUsesInterrupts have been converted to the corresponding
rtems_termios_device_mode enum value, conversions from
deviceOutputUsesInterrupts have been made explicit, and uses of
rtems_termios_device_mode enum values with deviceOutputUsesInterrupts
have been converted to booleans.
|
|
When encountering an error during filesystem creation, fat_fd must be
cleaned up appropriately once the file is opened. There was an
opportunity for a resource leak due to jumping to the incorrect error
handling label.
|
|
An error is already being reported. Checking the return value of this
function is not useful.
|
|
Revert JFFS2 to non-granular locking. This makes the superblock
available to the delayed work that it owns so that delayed work
processing can ensure that shared resources are being exclusively
accessed. This change only affects NAND systems. Moving forward with
granular locking will require a significant investment of time in
producing a test harness that doesn't require hardware such that this
can get a reasonable amount of test coverage.
|
|
A verbose verbosity is not required for normal test suite runs. It may
be used to debug test cases.
|
|
Document CONFIGURE_JFFS2_DELAYED_WRITE_TASK_PRIORITY.
Update #4961.
|
|
The TM27 support may define TM27_INTERRUPT_VECTOR_ALTERNATIVE to provide
an alternative software generated interrupt request which is raised by
_TM27_Raise_alternative() and cleared by _TM27_Clear_alternative().
Both functions shall return an RTEMS status code. This interrupt vector
may be used to test the interrupt controller support on targets which do
not provide generic software generated interrupts.
Update #3716.
|
|
Let the BSP define TM27_INTERRUPT_VECTOR_DEFAULT to more efficiently and
reliably get the TM27 default interrupt vector.
Update #3716.
|
|
|
|
Route the test output through T_vprintf() only while the test suite
runs. Otherwise, the begin/end of test message may not show up.
|
|
Route the test output through T_vprintf().
|
|
This feature is not supported by lwIP.
|
|
|
|
- Extend the timeout to 150 msec for long remote sessions
- Improve the performance of the detection
Closes #4975
Closes #4977
|
|
This helps to validate that the data was transferred correctly.
|
|
This can be used to report that nested test cases did run in a test
case.
Update #4971.
|
