summaryrefslogtreecommitdiffstats
path: root/cpukit/dev/Makefile.am (unfollow)
Commit message (Collapse)AuthorFilesLines
2018-10-09build: Merge dev/Makefile.amSebastian Huber1-23/+0
2018-01-25Remove make preinstallChris Johns1-34/+0
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.
2017-10-02i2c: Add temperature sensor LM75A driverSebastian Huber1-0/+2
Close #3163.
2017-08-20dev/i2c: Add I2C device support for FPGA Slave, LM25066A, TMP112, ADS1113, ↵Chris Johns1-0/+8
ADS1114 and ADS1115 Closes #3101.
2017-08-16dev/i2c: Add Xilinx AXI I2C driver.Chris Johns1-0/+2
This is a generic driver for use with Xilinx AXI I2C controller IP. Closes #3100.
2016-12-16dev: Add NXP SC16IS752 serial device driverAlexander Krutwig1-0/+7
Update #2841.
2016-09-16Add SPI bus frameworkAlexander Krutwig1-0/+9
User API is compatible to Linux userspace API. New test libtests/spi01. Update #2776.
2014-11-20Add NXP PCA9548A 8-channel switch I2C driverSebastian Huber1-0/+2
2014-11-20Add NXP PCA9535 16-bit GPIO I2C driverSebastian Huber1-0/+2
2014-11-20Add generic EEPROM I2C device driverSebastian Huber1-0/+2
2014-11-20Add I2C driver frameworkSebastian Huber1-0/+11
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).
2014-11-20Add RTEMS port of Linux I2C user-space APISebastian Huber1-0/+12