OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/kernel/nanokernel/Makefile

19 lines
630 B
Makefile
Raw Normal View History

Use ccflags-y and asflags-y instead of EXTRA_CFLAGS According to section 3.7 of Documentation/kbuild/makefiles.txt, using EXTRA_CFLAGS in Makefiles is "still supported but their usage is deprecated." However, using make EXTRA_CFLAGS="-DSOMETHING" results in EXTRA_CFLAGS from Makefiles being overwritten, obviously breaking the build. This patch converts to them to the newer ccflags-y which also fixes the problem. Change-Id: I6309439599d4c9cc184f9ecd941bde841982ef07 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-06-04 10:17:57 +08:00
ccflags-y +=-I$(srctree)/kernel/nanokernel/include
ccflags-y +=-I$(srctree)/kernel/microkernel/include
Kbuild: adapt Makefile/Kconfig to core/ removal Change-Id: I96f8a1798e8d84a4876bcb59f5b93ec134e9a233 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-10 00:05:47 +08:00
Use ccflags-y and asflags-y instead of EXTRA_CFLAGS According to section 3.7 of Documentation/kbuild/makefiles.txt, using EXTRA_CFLAGS in Makefiles is "still supported but their usage is deprecated." However, using make EXTRA_CFLAGS="-DSOMETHING" results in EXTRA_CFLAGS from Makefiles being overwritten, obviously breaking the build. This patch converts to them to the newer ccflags-y which also fixes the problem. Change-Id: I6309439599d4c9cc184f9ecd941bde841982ef07 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-06-04 10:17:57 +08:00
asflags-y := ${ccflags-y}
Kbuild: adapt Makefile/Kconfig to core/ removal Change-Id: I96f8a1798e8d84a4876bcb59f5b93ec134e9a233 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-10 00:05:47 +08:00
Kbuild: rename nanokernel files Change-Id: I69edff76922c1dd4f48cf34579bb326ff021d115 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 09:56:26 +08:00
obj-y = nano_fiber.o nano_lifo.o \
nanokernel: allow nano time tracking to be used in microkernels The nanokernel time tracking code (ticker) can now exist in microkernel systems. This allows the ticker that drives nano timers and timeouts to advance the tick count for these in a microkernel, thus allow their presence there. Previously, nano timers could not be used in a microkernel. Change-Id: I17f2b659691a081b0f9bf3961ed030533aa02a15 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-06-15 06:12:14 +08:00
nano_fifo.o nano_stack.o nano_sys_clock.o \
Kbuild: rename nanokernel files Change-Id: I69edff76922c1dd4f48cf34579bb326ff021d115 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-15 09:56:26 +08:00
nano_context.o nano_init.o nano_sema.o \
Remove obsolete ctors section Remove prototype support for C++ constructors, since it is not well designed. Device drivers (or other application code) that requires an automatic initialization capability should use the device initialization macros instead. Note: Support for C++ constructors may be re-introduced at a later date. However, a number of issues need to be settled, such as when the constructors are invoked and what context they run in. (Running them during nanokernel initialization, as was previously done, is probably not the right approach.) Change-Id: If6d27ac16b485cb39d5ec34084e9d0f1991074f4 Signed-off-by: Peter Mitsis <peter.mitsis@windriver.com>
2015-10-21 23:28:10 +08:00
version.o device.o
Kbuild: adapt Makefile/Kconfig to core/ removal Change-Id: I96f8a1798e8d84a4876bcb59f5b93ec134e9a233 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-05-10 00:05:47 +08:00
obj-$(CONFIG_STACK_CANARIES) += compiler_stack_protect.o
obj-$(CONFIG_INT_LATENCY_BENCHMARK) += int_latency_bench.o
obj-$(CONFIG_ADVANCED_POWER_MANAGEMENT) += idle.o
nanokernel: add NANO_TIMERS option The nanokernel timers will be available in the microkernel, but can be disabled if not needed. A kconfig option is needed for that: the option is enabled by default, and only available in the nanokernel for now. It will be made available in the microkernel in the future. Change-Id: I3910affde7bd2e7b25ab0a3c655255a9be01c9b8 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-06-15 04:06:28 +08:00
obj-$(CONFIG_NANO_TIMERS) += nano_timer.o
Add event logger. Add a log event tool with a single interface for the user to add/collect the event log data. Change-Id: Ia4b78836748c5d7e44ba1bdd50c28434e8a55d65 Signed-off-by: Yonattan Louise <yonattan.a.louise.mendoza@intel.com>
2015-08-12 02:32:16 +08:00
obj-$(CONFIG_EVENT_LOGGER) += event_logger.o
Rename Profiler to Event Logger. In order to have a name according to the functionality of the feature. This commit rename any text, function and variable related with the Profiler name to Event logger. Change-Id: I4f612cbc7c37965c35a64f06cc3ce5e3249d90e5 Signed-off-by: Yonattan Louise <yonattan.a.louise.mendoza@intel.com>
2015-10-17 04:45:02 +08:00
obj-$(CONFIG_KERNEL_EVENT_LOGGER) += kernel_event_logger.o
nanokernel: add optional ring buffer data type This patch is based on some code contributed by Dirk Brandewie. This is a generic data structure for queuing data in a FIFO ring buffer. Any given data enqueued is annotated with an app-specific type identifier, and small integral value. Use of a data pointer is optional if the necessary information can be conveyed in the annotations. We want all the metadata to fit in a single DWORD. The ring buffer always contains at least one free dword in the buffer to correctly distinguish between full and empty queues. Concurrency control is almost nonexistent; depending on usage, apps may want to introduce the usage of semaphores and/or mutexes to preserve the integrity of the ring buffer or provide notifications when data is available. Change-Id: I860262d2afc96db4476d4c695a92f7da355ab732 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2015-08-28 04:07:36 +08:00
obj-$(CONFIG_RING_BUFFER) += ring_buffer.o