| Age | Commit message (Collapse) | Author |
|---|
|
The function rtems_rfs_buffer_sync() erroneously calls
rtems_disk_release(). This screws up the reference counting of the disk.
Close #3494.
|
|
Closes #3324
|
|
Handles possible NULL return value
Updates #2747
|
|
POSIX specifies char *, not const char *
Updates #2747
|
|
Updates #2747
|
|
Updates #2747
|
|
If there is already a file with a long file name it isn't possible to
create a second file which has a name that ends on the first files name
(for example ets.beam and sets.beam). This patch fixes that.
Close #3258.
|
|
Take care that a file in the root directory with the same name as the
volume name can be found.
Close #3257.
|
|
Close #3164.
|
|
The RTEMS_MILLISECONDS_TO_TICKS() macro doesn't round up. Do not use it
to calculate the program timeout in ticks. Check program done condition
after the timeout check to account for pre-emptions.
Close #3162.
|
|
Close #3161.
|
|
Do not update the non-existant meta-data of the root directory.
Close #2944.
|
|
Close #2964.
|
|
Set a proper name buffer length for each converter invocation.
Close #2987.
|
|
- Add 'rtems_shell_init_environment()' so a user can create the
shell environment without needing to run a shell.
- Move 'rtems_shell_lookup_topic', 'rtems_shell_can_see_cmd',
and 'rtems_shell_execute_cmd' from the internal interface to
the public interface.
Closes #3104.
|
|
Remove the OBJECTS_UNLIMITED_OBJECTS flag for the memory size
configuration.
Close #3105.
|
|
Close #3093.
|
|
Do not touch the FPSCR[QC] bit since this is DNM/RAZ on Cortex-R4.
Close #3092.
|
|
Right after a "msr basepri_max, %[basepri]" instruction an interrupt
service may still take place (observed at least on Cortex-M7). However,
pendable service calls that are activated during this interrupt service
may be delayed until interrupts are enable again. The
_ARMV7M_Pendable_service_call() did not check that a thread dispatch is
allowed. Move this test from _ARMV7M_Interrupt_service_leave() to
_ARMV7M_Pendable_service_call().
Close #3060.
|
|
Closes #2956.
|
|
Do not use our long file name entry count to optimize the file name
search. The Unicode comparison must be taken into account.
Close #2939.
|
|
Obtain file system instance lock before member access.
Close #2937.
|
|
The name "fat_entries" for long file name directory entries is quite
misleading.
|
|
Close #2934.
|
|
Simplify.
|
|
Make sure that long file names work accross cluster boundaries.
Close #2929.
|
|
Update #2929.
|
|
Update #2929.
|
|
Update #2929.
|
|
Update #2929.
|
|
Remove forced overwrite which leads to file data corruption. The logic
to determine a forced overwrite was fundamentally broken. For simplity,
disable this feature.
Close #2622.
|
|
It is all right in case the result uses the full destination buffer.
Without this fix the handling of a maximum 8.3 short file name is
broken.
Close #2928.
|
|
Perform a context-dependent deferred location release to avoid a
deadlock on the file system instance locks, for example during a
chdir().
Close #2936.
|
|
In canonical mode, the raw input buffer or the canonical buffer may
overflow without an end of line. Avoid an infinite loop in this case.
Update #2915.
|
|
Use the device lock to protect the raw input buffer management, e.g.
tail, head and buffer content updates.
Update #2914.
|
|
Remove dead code.
Update #2914.
|
|
The second FAT entry contains a bit to indicate if the FAT32 filesystem
is not dirty and a bit to indicate if there was no IO error. Set both
bits for a fresh filesystem. This prevents a warning if mounted on
Windows.
Update #2913.
|
|
Update #2755.
|
|
Close #2388.
|
|
Close #2401.
|
|
For a filename match the entry must match without anything remaining.
Update #2908.
|
|
Update #2886.
|
|
CPU_STRUCTURE_ALIGNMENT.
|
|
The CPU_CACHE_LINE_BYTES has been introduced after 4.11 branch
fork and is not available for all architectures on RTEMS 4.11.
Use of rtems_cache_get_maximal_line_size() is more descriptive
choice. The min/max data/instruction cache line size is not critical
there, value is used for optimization only to use single operation
for decently following sections.
|
|
Memory content changes caused by relocation has to be
propagated to memory/cache level which is used/snooped
during instruction cache fill.
Closes #2438
Updates #2782
|
|
and maximal alignment.
There is need for unambiguous named and defined cache function
which should be called when code is updated, loaded
or is self-modifying.
There should be function to obtain maximal cache line length
as well. This function can and should be used for allocations
which can be used for data and or code and ensures that
there are no partial cache lines overlaps on start and
end of allocated region.
Updates #2782
|
|
Some/many Cortex-A cores have data cache line length 64 bytes and maximum
value has to be used for system structures alignment.
Updates #2782
Updates #2783
|
|
base access.
The main reason for inclusion of minimum hypervisor related defines
is that current ARM boards firmware and loaders (U-boot for example)
start loaded operating system kernel in HYP mode to allow it take
control of virtualization (Linux/KVM for example).
Updates #2783
|
|
Only use CPU_Per_CPU_control if it contains at least one filed. In GNU
C empty structures have a size of zero. In C++ structures have a
non-zero size. In case CPU_PER_CPU_CONTROL_SIZE is defined to zero,
then this structure is not used anymore.
Close #2789.
|
|
This patch fixes a number of bugs in the cache when requests are
made to read close to the end of the file and the data is copied
from the top of the cache buffer to the bottom of the buffer. This
was compounded by attempting to read past the end of the file.
Closes #2754.
|
