zephyr/tests/net/buf/Makefile

BOARD ?= qemu_x86
CONF_FILE = prj.conf

include $(ZEPHYR_BASE)/Makefile.test
Use BOARD instead of PLATFORM_CONFIG Change-Id: I14db0087cd705df0db8a911071bc3949b5c79314 Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2015-12-14 04:00:31 +08:00			`BOARD ?= qemu_x86`
tests: remove duplicate kernel configs and usage of ARCH Many test configs are the same, remove complexity and duplication by using just one kernel config where applicable. This removes the usage of ARCH which is a remnant from the days where we had to specify the architecture of the board, the architecture is now part of Kconfig and determined basded on the board configuration. This will also make it easy adding new architectures to test cases without having to add an architecture specific config file when it is actually not needed, for example now that we will enable micro-kernel support on ARC. Jira: ZEP-238 Change-Id: I143fa3c4629c58329cfeb0c761c7a896fc1ef63a Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-05-21 19:24:23 +08:00			`CONF_FILE = prj.conf`
net: Add initial generic buffer implementation We need to have a generic buffer API in order to efficiently transfer data between different subsystems. The first such case will be the Networking and Bluetooth subsystems where 6LoWPAN data will be passed back and forth. The needed API needs to provide enough flexibility for different buffer sizes as well as custom protocol-specific context data. The implementation offered in this patch follows the general design of the existing Networking and Bluetooth buffer implementations by using a backing array of buffer which is fed into a "free buffers" FIFO for management. The main difference is that the API allows specifying variable sized buffers for each created pool, as well as a minimum amount of "user data" that's allocated as part of each buffer. There's also an optional destroy callback that's e.g. useful for HCI flow control in Bluetooth (for notifying the controller of available buffers). Change-Id: I00b7007135a0ff35219f38f48658f31728fbb7ca Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 2015-10-07 23:32:54 +08:00
tests: introduce Makefile.test To customise test builds and support test related features such as time stamps and a boot banner, introduce a Makefile variant that is dedicated to testing. Initially we introduce a new config overlay that is used for all tests, in this case we enable BOOT_BANNER and BUILD_TIMESTAMP. This will print the current version and the date, useful when reporting bugs and also an indicator that the system has booted before the test has started. For example: [QEMU] CPU: qemu32 *** BOOTING ZEPHYR OS v1.6.99 - BUILD: Dec 21 2016 19:57:13 *** tc_start() - Test Nanokernel CPU and thread routines Initializing nanokernel objects ... .. Change-Id: I224318cdeb55a301964ea366dbc577e2e3a09175 Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-12-22 03:38:37 +08:00			`include $(ZEPHYR_BASE)/Makefile.test`