| Age | Commit message (Collapse) | Author |
|---|
|
Use the following variant which was already used by most source files:
#ifdef HAVE_CONFIG_H
#include "config.h"
#endif
|
|
This may help to avoid character loss.
|
|
Ensures that the FCR values are used.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This work was performed as a GCI 2018 task.
|
|
|
|
Avoid division by zero and instead disable rx/tx in case of a zero baud
value. Problem identified by Coverity Scan.
|
|
The field names for the registers generated a name collision (MSR_RI on
the power pc). This patch adds a SC16IS752_ prefix for all field names.
Closes #3501.
|
|
This add ths following ioctl calls to the sc16is752 driver:
- TIOCMGET
- TIOCMSET
- TIOCMBIS
- TIOCMBIC
|
|
Escalate a failed installation of the interrupts to the next higher
level.
|
|
|
|
Update #2843.
|
|
Update #2843.
|
|
Setting the PIRQ to 0 before reading the data produces a short clock pulse.
Moving the write to after reading the data fixes the issue.
Close #3173
|
|
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.
|
|
Close #3163.
|
|
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.
Update #3162.
|
|
Update #3161.
|
|
|
|
Update #2133.
|
|
Update #3082.
|
|
ADS1114 and ADS1115
Closes #3101.
|
|
This is a generic driver for use with Xilinx AXI I2C controller IP.
Closes #3100.
|
|
|
|
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
|
|
Update #2897.
|
|
Update #2841.
|
|
User API is compatible to Linux userspace API. New test libtests/spi01.
Update #2776.
|
|
|
|
|
|
This reduces the average node size.
Add and use IMFS_GENERIC_INITIALIZER().
|
|
|
|
|
|
Coverity ID 1255520. fd was not closed on error path.
|
|
|
|
|
|
|
|
|
|
This I2C driver framework has some major differences compared to libi2c.
* It is compatible to the Linux I2C user-space API.
* It uses generic IMFS nodes and thus reduces the levels of indirection.
* The drivers don't have to mess around with minor numbers to get their
state information.
* No arbitrary bus controller model is assumed. The main task of an I2C
bus controller driver is to process I2C messages. How this is done is
private to the driver.
* Scatter/gather operations are supported (I2C_M_NOSTART).
|
|
|
