zephyr/tests/drivers/spi_test/Makefile

BOARD ?= quark_se_c1000_devboard
KERNEL_TYPE = nano
CONF_FILE = prj.conf

include ${ZEPHYR_BASE}/Makefile.inc
boards: rename Quark SE Devboard to Quark SE C1000 This board now has an official name and will be available soon: http://www.intel.com/content/www/us/en/embedded/products/quark/mcu/se-soc/overview.html Jira: ZEP-758 Change-Id: Ia16d33722308cf81471321c3063bdc75055a4d50 Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-08-30 20:41:04 +08:00			`BOARD ?= quark_se_c1000_devboard`
samples: Add a q&d test application for SPI A dummy test to verify SPI driver and API build properly. Change-Id: Icb1ab282b4a0fa02ec949c96becdfdc16f20bc2d Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com> 2016-01-25 17:21:51 +08:00			`KERNEL_TYPE = nano`
samples: get rid of obsolete usage of ARCH variable Using ARCH variable to select different configurations for the different architectures is misleading and conflicts with the variable ARCH being used by the build system. The variable is not needed, it is application specific and an application can be built without the need to specify ARCH on the command line. This is yet another item specific to samples and test cases that wrongfully being used and documented for every application. We need to use another variable and just make it clear it is specific to samples and how they are written. One possible solution is to have a script that gets the architecture based on the board being used. Attachments Jira: ZEP-238 Change-Id: Ieccbc087a41858fb96fb361c0aaa04705e968a4e Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-05-12 08:22:01 +08:00			`CONF_FILE = prj.conf`
samples: Add a q&d test application for SPI A dummy test to verify SPI driver and API build properly. Change-Id: Icb1ab282b4a0fa02ec949c96becdfdc16f20bc2d Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com> 2016-01-25 17:21:51 +08:00
			`include ${ZEPHYR_BASE}/Makefile.inc`