zephyr/tests/net/buf/Makefile

BOARD ?= qemu_x86
KERNEL_TYPE ?= unified
CONF_FILE = prj.conf

include $(ZEPHYR_BASE)/Makefile.inc
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`
ztest: move ztest to unified kernel ztest was not working with unified kernel and v1 APIs and not many tests are using ztest right now, so instead of making it work with old APIs, convert it to unified kernel completely so that new tests written using ztest would be unified kenrel based. Change-Id: Ibfcc7783dcb266abbd388662ba61c4b55d32b10c Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2016-10-29 02:44:17 +08:00			`KERNEL_TYPE ?= unified`
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
			`include $(ZEPHYR_BASE)/Makefile.inc`