summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* smpmulticast01: Fix NULL pointer accessSebastian Huber2020-11-101-1/+1
|
* Add correct link address for griscv waf buildJiri Gaisler2020-11-092-0/+6
|
* Add networking support for griscv bspJiri Gaisler2020-11-098-14/+117
| | | | | | | * Only GRETH device supported for now * Fix endian problem in GRETH driver * Remove SPARC assembly from greth.c * Builds with both autoconf and waf
* libtrace: Move _Record_Stream_header_initialize()Sebastian Huber2020-11-094-106/+142
| | | | This fixes the build if no function sections are used.
* sparc: Add SPARC_INTERRUPT_SOURCE_TO_TRAP()Sebastian Huber2020-11-064-3/+15
| | | | Update #4171.
* sparc: Add SPARC_INTERRUPT_TRAP_TO_SOURCE()Sebastian Huber2020-11-067-6/+23
| | | | Update #4171.
* sparc: Add SPARC_IS_INTERRUPT_TRAP()Sebastian Huber2020-11-067-27/+29
| | | | Update #4171.
* sparc: Move SPARC-specific macros to sparc.hSebastian Huber2020-11-062-22/+40
| | | | | | Clarify Doxygen comments. Fix formatting. Update #4171.
* rtems-bsps: Use build specification itemsSebastian Huber2020-11-051-13/+18
| | | | Close #4123.
* build: Place cache file in output directorySebastian Huber2020-11-051-2/+2
| | | | | | | | This improves support for the --out option. Previously, the cache file was placed in the source directory under "build/...". Now, it is placed in the output directory, which is "build" by default. So, if you don't use the --out option nothing changes. However, if you use the --out option, then the cache file is placed under the specified directory.
* confdefs: Add extern C guards to libpci.hJan Sommer2020-10-301-0/+8
|
* score: Fix unused parameter 'lock' warningSebastian Huber2020-10-281-0/+1
|
* build: Improve cache handlingSebastian Huber2020-10-281-1/+4
| | | | Check the directory modification time to notice file removals.
* build: Report caching errorsSebastian Huber2020-10-281-1/+1
| | | | | The ctx.fatal() method uses an exception to stop the build. Do not catch it.
* bsp/stm32h7: New BSPSebastian Huber2020-10-2768-0/+4813
| | | | Update #3910.
* bsp/stm32h7: Fix warningsSebastian Huber2020-10-272-15/+15
| | | | Update #3910.
* bsp/stm32h7: Disable unused functionsSebastian Huber2020-10-275-0/+28
| | | | Update #3910.
* bsp/stm32h7: Enable LL driversSebastian Huber2020-10-2746-88/+88
| | | | Update #3910.
* bsp/stm32h7: Move <math.h> includeSebastian Huber2020-10-273-1/+2
| | | | | | This is necessary for libbsd compatibility. Update #3910.
* bsp/stm32h7: Constify some functionsSebastian Huber2020-10-276-12/+12
| | | | Update #3910.
* bsp/stm32h7: Import from STM32CubeMX-5.6.0Sebastian Huber2020-10-27259-0/+706411
| | | | Update #3910.
* bsp/leon3: Updat due to API changesSebastian Huber2020-10-261-1/+1
|
* bsps/arm: Sort fast text/data sectionsSebastian Huber2020-10-211-2/+2
|
* bsps/arm: Add support for MPU region alignmentSebastian Huber2020-10-211-0/+21
| | | | Update #3910.
* rtems-fdt / shell - Fix string truncation warningFrank Kühndel2020-10-201-21/+19
| | | | | | | | | | | | | | The compiler warning was: ../../../cpukit/libmisc/rtems-fdt/rtems-fdt.c:267:5: warning: 'strncpy' specified bound depends on the length of the source argument 267 | strncpy(path, name, namelen); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ It turns out that the `strncpy()` nor the buffer `path` is needed when one uses `strncmp()` instead of `strcmp()`. This needs some change to the algorithm but has the advantage that `name` is never truncated to the size of the buffer `path`.
* bsps: Fix rtems_interrupt_server_delete()Sebastian Huber2020-10-191-0/+2
| | | | | | | The ISR lock must be destroyed to prevent memory corruption if RTEMS_PROFILING and RTEMS_SMP is enabled. Close #4158.
* posix: Fix pthread_spin_unlock()Sebastian Huber2020-10-191-1/+1
| | | | | | | Prevent a call to _SMP_lock_Stats_register_or_max_section_time(). This fixes a thread stack corruption in case RTEMS_PROFILING and RTEMS_SMP is enabled. Close #4157.
* libfs/rfs: Check search bit map end on last bitChris Johns2020-10-171-2/+15
| | | | | | | - Do not write past the last location of the search bit map whe nit is being created. Closes #4148
* grlib: Add ambapp_common_info to derived typesSebastian Huber2020-10-1614-50/+46
| | | | This avoids a cast in DEV_TO_COMMON().
* grlib: Remove unused conversion macrosSebastian Huber2020-10-161-5/+0
|
* grlib: Remove superfluous forward declsSebastian Huber2020-10-161-5/+0
|
* bsps/arm: Add workaround for Errata 794072Sebastian Huber2020-10-161-0/+16
| | | | | | | | Add a workaround for Cortex-A9 Errata 845369: A short loop including a DMB instruction might cause a denial of service on another which executes a CP15 broadcast operation. Close #4115.
* bsps/arm: Workaround for Errata 845369Sebastian Huber2020-10-162-0/+47
| | | | | | | Add a workaround for Cortex-A9 Errata 845369: Under Very Rare Timing Circumstances Transition into Streaming Mode Might Create Data Corruption. Update #4115.
* Revert "rtems-fdt / shell - Fix string truncation warning"Sebastian Huber2020-10-161-19/+21
| | | | This reverts commit 355bc37ad35a7d67a7209130171febe805c67f62.
* rtems-fdt / shell - Fix string truncation warningFrank Kühndel2020-10-151-21/+19
| | | | | | | | | | | | | | | | | | | | | The compiler warning was: ../../../cpukit/libmisc/rtems-fdt/rtems-fdt.c:267:5: warning: 'strncpy' specified bound depends on the length of the source argument 267 | strncpy(path, name, namelen); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ It turns out that the `strncpy()` nor the buffer `path` is needed when one uses `strncmp()` instead of `strcmp()`. This needs some change to the algorithm but has the advantage that `name` is never truncated to the size of the buffer `path`. Note: rtems-fdt.c, rtems-fdt-shell.c and cpukit/include/rtems/rtems-fdt.h seem to be dead code. They implement a shell command `fdt` but that command is not part of the shell nor of any macro in cpukit/include/rtems/shellconfig.h.
* shell/main_edit.c: Fix string truncation warningFrank Kühndel2020-10-151-5/+7
| | | | | | | | | | | | Using strlcpy() instead of strncpy(): 1) Prevents the compiler warnings 2) Ensures, the string is NUL terminated. 3) Avoids that strncpy() unnecessary fills the unused part of the buffer with 0 bytes. (Note that realpath() also returns NULL if the file does not exist - that happens always if someone creates a new file with the editor of the shell.)
* shell/main_edit.c: Fix use of wrong constantFrank Kühndel2020-10-151-1/+2
| | | | | realpath() requires a buffer of size PATH_MAX and not of size FILENAME_MAX according to 'man realpath (3)'.
* shell/shell.c: Fix illegal string copyFrank Kühndel2020-10-151-4/+14
| | | | | | | | | | | | | This is an illegal use of strcpy() because one is not allowed to use this function with overlapping source and destination buffers; whereas memmove() is explicitly designed to handle such cases. The copiler warning was: ../../../cpukit/libmisc/shell/shell.c:626:13: warning: 'strcpy' accessing between 1 and 2147483645 bytes at offsets 0 and [1, 2147483647] may overlap up to 2147483644 bytes at offset [1, 2147483644] [-Wrestrict]
* shell/shell.c: Fix an implicit type castFrank Kühndel2020-10-151-1/+3
| | | | | With some compiler warnings enabled, the implicit cast may trigger a compiler warning. The explicit cast avoids this.
* fsdosfsname01: Fix string truncation warningFrank Kühndel2020-10-151-6/+7
| | | | | | | | | | | | | | | This patch fixes a compiler warning: ../../../testsuites/fstests/fsdosfsname01/init.c:430:19: warning: '%s' directive output may be truncated writing up to 6424 bytes into a region of size 257 [-Wformat-truncation=] The buffer 'dirname' is exactly large enough so that no truncation can ever occur. Using the return value of snprintf() is an official supported way to suppress the warning. I considered the comment of Joel Sherrill about not replacing snprintf(): https://lists.rtems.org/pipermail/devel/2020-September/062113.html
* Remove *_Is_null() inline functionsSebastian Huber2020-10-1412-72/+16
| | | | Simply compare the values against NULL.
* rtems: Remove superfluous includeSebastian Huber2020-10-141-2/+0
|
* lpc32xx_mzx_stage_1-testsuite.tcfg: Add ttest01Joel Sherrill2020-10-121-0/+1
|
* lpc2362-testsuite.tcfg: Add monitor and psxmsgq01Joel Sherrill2020-10-121-0/+2
|
* lm3s3749-testsuite.tcfg: Add spcxx01Joel Sherrill2020-10-121-0/+1
|
* build: Move drivers without SMP supportSebastian Huber2020-10-122-15/+33
| | | | | | | | This fixes warnings like this: warning: implicit declaration of function 'rtems_interrupt_disable' warning: implicit declaration of function 'rtems_interrupt_enable' warning: implicit declaration of function 'rtems_interrupt_flash'
* build: Fix formatSebastian Huber2020-10-1210-16/+18
|
* testsuites/samples/fileio - Increase of stack sizeFrank Kühndel2020-10-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | When I use the 'shell' from the fileio sample with the command below: env QEMU_AUDIO_DRV="none" \ qemu-system-arm -no-reboot -net none -nographic -M realview-pbx-a9 \ -m 256M \ -kernel build/arm/realview_pbx_a9_qemu/testsuites/samples/fileio.exe The executable crashes with an "BLOWN STACK!!!" as soon as I try to login as 'root' with password. (The logins without password work fine.) Increasing the stack size of the affected thread a bit solves the issue. Hence, I suggest this patch. My config.ini was [arm/realview_pbx_a9_qemu] RTEMS_DEBUG = True RTEMS_NETWORKING = True RTEMS_POSIX_API = True RTEMS_SMP = True BUILD_TESTS = True RTEMS origin.master at a479686c112144119866391ceb21c48be6a3eca9 Close #4143
* shell: Remove not functioning fdisk mount/unmountFrank Kühndel2020-10-125-255/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The shell has an 'fdisk' command which has sub-commands 'mount' and 'unmount'. These two sub-commands have a bug which causes them to be not able to mount anything. This proposed patch removes the buggy file cpukit/libblock/src/bdpart-mount.c and the mount/unmount commands from 'fdisk' as bug fix. The 'fdisk' command itself is not removed. The reasons for removing the sub-commands (instead of fixing the issue) are: 1) The bug has been introduced on 2010-May-31 with commit 29e92b090c8bc35745aa5c89231ce806bcb11e57. Since ten years no one can use this feature, nor has anybody complained about it. 2) Besides of the 'fdisk' 'mount' sub-command, the shell has the usual 'mount' and 'unmount' commands which can serve as substitutes. 3) There are additional minor issues (see further down) which needed to be addressed when the file will be kept. What follows below is the precise bug description. The bug is in function rtems_bdpart_mount() which is only be used by the 'fdisk' shell command to mount all partitions of a disk with a single command: > fdisk DISK_NAME mount > mounts the file system of each partition of the disk > > fdisk DISK_NAME unmount > unmounts the file system of each partition of the disk The whole command does not work because in file cpukit/libblock/src/bdpart-mount.c line 103 specifies the file system type of each partition to be "msdos". Yet, "msdos" does not exist. The name must be "dosfs". Beside of this fundamental problem, there are more issues with the code in bdpart-mount.c: 1) The function returns RTEMS_SUCCESSFUL despite the mount always fails. 2) The reason for errors is not written to the terminal. 3) The directory '/mnt' is created but not deleted later on (failure or not). 3) There is no documentation about this special 'fdisk' feature in the RTEMS Shell Guide ('fdisk' is mentioned but its documentation is a bit short): https://docs.rtems.org/branches/master/shell/ file_and_directory.html#fdisk-format-disk 4) Only "msdos" formatted partitions can be mounted and all partitions are mounted read-only. This is hard coded and cannot be changed by options. Moreover, there is no information about this to the user of the shell (i.e. using 'fdisk' mount requires insider knowledge). How to reproduce: 1) For testing, I use the 'testsuites/samples/fileio.exe' sample with qemu: > cd rtems > env QEMU_AUDIO_DRV="none" qemu-system-arm -net none -nographic \ > -M realview-pbx-a9 -m 256M -kernel \ > build/arm/realview_pbx_a9_qemu/testsuites/samples/fileio.exe 2) Type any key to stop the timer and enter the sample tool. Type 's' to enter the shell, login as 'root' with the password shown in the terminal. 3) Type the following shell commands (they create a RAM disk, partition it, register it, format it and try to mount it): > mkrd > fdisk /dev/rda fat32 16 write mbr > fdisk /dev/rda register > mkdos /dev/rda1 > fdisk /dev/rda mount 4) The last line above is the command which fails - without an error message. There exists a '/mnt' directory but no '/mnt/rda1' directory as it should be: > ls -la /mnt 5) If you change line 103 of 'cpukit/libblock/src/bdpart-mount.c' from "msdos" to "dosfs", compile and build the executable and re-run the above test, '/mnt/rda1' exists (but the file system is mounted read-only). Close #4131
* cpukit/libmisc/monitor: Fix an illegal string copyFrank Kühndel2020-10-121-1/+2
| | | | | | | | | | | | This is actually an illegal use of strcpy() because one is not allowed to use this function with overlapping source and destination buffers; whereas memmove() is explicitly designed to handle such cases. The compiler warning was: ../../../cpukit/libmisc/monitor/mon-editor.c:342:15: warning: 'strcpy' accessing 1 byte at offsets [0, 75] and [0, 75] overlaps 1 byte at offset [0, 74] [-Wrestrict]
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-06 02:15:56 +0000