| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Update #3706.
|
|
This makes the @file documentation independent of the actual file name.
Update #3707.
|
|
|
|
|
|
Update #3358.
|
|
Update #3358.
|
|
Update #2843.
|
|
A speciality of the RTEMS build system was the make preinstall step. It
copied header files from arbitrary locations into the build tree. The
header files were included via the -Bsome/build/tree/path GCC command
line option.
This has at least seven problems:
* The make preinstall step itself needs time and disk space.
* Errors in header files show up in the build tree copy. This makes it
hard for editors to open the right file to fix the error.
* There is no clear relationship between source and build tree header
files. This makes an audit of the build process difficult.
* The visibility of all header files in the build tree makes it
difficult to enforce API barriers. For example it is discouraged to
use BSP-specifics in the cpukit.
* An introduction of a new build system is difficult.
* Include paths specified by the -B option are system headers. This
may suppress warnings.
* The parallel build had sporadic failures on some hosts.
This patch removes the make preinstall step. All installed header
files are moved to dedicated include directories in the source tree.
Let @RTEMS_CPU@ be the target architecture, e.g. arm, powerpc, sparc,
etc. Let @RTEMS_BSP_FAMILIY@ be a BSP family base directory, e.g.
erc32, imx, qoriq, etc.
The new cpukit include directories are:
* cpukit/include
* cpukit/score/cpu/@RTEMS_CPU@/include
* cpukit/libnetworking
The new BSP include directories are:
* bsps/include
* bsps/@RTEMS_CPU@/include
* bsps/@RTEMS_CPU@/@RTEMS_BSP_FAMILIY@/include
There are build tree include directories for generated files.
The include directory order favours the most general header file, e.g.
it is not possible to override general header files via the include path
order.
The "bootstrap -p" option was removed. The new "bootstrap -H" option
should be used to regenerate the "headers.am" files.
Update #3254.
|
|
Prepare for header file move to common include directory.
Update #3254.
|
|
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.
Update #3258.
|
|
Take care that a file in the root directory with the same name as the
volume name can be found.
Update #3257.
|
|
Update #3132.
|
|
Do not update the non-existant meta-data of the root directory.
Update #2944.
|
|
Update #2964.
|
|
Set a proper name buffer length for each converter invocation.
Update #2987.
|
|
Close #3003.
|
|
Added a mmap file handler to struct _rtems_filesystem_file_handlers_r.
Updated each file handler object to support the default mmap handler.
Updated mmap() to call the mmap handler for MAP_SHARED.
Added a mmap file handler for shm
Added support for MAP_ANON in mmap().
Updates #2859
|
|
Do not use our long file name entry count to optimize the file name
search. The Unicode comparison must be taken into account.
Update #2939.
|
|
Obtain file system instance lock before member access.
Update #2937.
|
|
The name "fat_entries" for long file name directory entries is quite
misleading.
|
|
Update #2934.
|
|
Simplify.
|
|
Make sure that long file names work accross cluster boundaries.
Update #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.
Update #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.
Update #2928.
|
|
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.
Close #2913.
|
|
Close #2755.
|
|
For a filename match the entry must match without anything remaining.
Close #2908.
|
|
Update #2803.
|
|
closes #2756,
|
|
Close #2727.
|
|
A cluster size > 32KiB resulted in an infinite loop in
fat_init_volume_info() due to an integer overflow.
Close #2717.
|
|
Drop superfluous <stdlib.h> include from <rtems/diskdevs.h> since this
leads to conflicts with the latest Newlib in case this header file is
used in the FreeBSD kernel space, e.g. for USB mass storage support.
|
|
|
|
|
|
|
|
|
|
|
|
Use the fstat handler instead.
|
|
|
|
CodeSonar flagged the increment of this pointer as unneeded. The pointer
is not used past this point.
|
|
CodeSonar flagged this as a case where the return value from fat_sync()
was not used. Now it is used to return pass/fail to the caller.
|
|
These were flagged by CodeSonar. The assignments on variable declaration
are overridden a few lines below and the other line later with name_size
is where name_size was not used after this assignment.
|
|
Coverity spotted that the return code from fat_set_fat_cluster()
was ignored. But it should be because we want to return the status
that caused us to hit the cleanup path.
|
|
Coverity identified that ret_val was never set except to be initialized
to 0. Thus the code could not be executed.
|
