Hi Kumar, This is to avoid undefined behaviour (exposed by DCE), example: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a3ca86aea507904148870946d599e07a340b39bf But the

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 1 [ZEP-430] Add driver API reentrancy support to PWM shim driver

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2433 : include/arch/arm/cortex_m/sys_io.h: added sys_write8 function, some socs need of byte wide addressing -

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 5 [ZEP-230] Define I2S driver APIs https://jira.zephyrproject.org/browse/ZEP-230 [ZEP-357] Support for the

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2431 : wdt : improve reentrancy of the wdt driver - https://gerrit.zephyrproject.org/r/2430 : pwm: prevent the corruption of global

I'll check the toolchain makefiles. Thanks! Renato

This appears to be taken directly from the Linux Kernel makefile, any idea why that was added over there? What all is in CLANG_FLAGS? Guessing this might be best added in

NEW JIRA items within last 24 hours: 2 [ZEP-428] Ethernet/IPv4/TCP net_send error https://jira.zephyrproject.org/browse/ZEP-428 [ZEP-429] CONFIG_NEWLIB_LIBC unusable with Zephyr SDK 0.8

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2366 : Bluetooth: Remove param from bt_conn_le_param_update - https://gerrit.zephyrproject.org/r/2365 : tests: fix build test

So, I found out about the linker problem: KFLAGS_*FLAGS go all the way to the assembler, but not the linker. Also, LDFLAGS is for LD, which is still GNU's, so I can't add Clang flags to it. But the

Hi Folks, I've been trying Clang builds with Zephyr and it seems that the Makefile has some support, but scattered all over the place and it doesn't handle the simple case any more. The use case is

Hi, Zephyr v1.4.0-rc2 has been tagged.  Remember that the target date for the 1.4.0 release is end of this week, don't forget to update your JIRAs items. Below is the list of changes since

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 1 [ZEP-424] AON counter driver needs to add driver API reentrancy support

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2349 : samples/task_profiler: remove "dump" logging - https://gerrit.zephyrproject.org/r/2346 : samples/task_profiler: modifications

NEW JIRA items within last 24 hours: 3 [ZEP-421] Application Development Primer Rewrite https://jira.zephyrproject.org/browse/ZEP-421 [ZEP-422] Cannot create Bluetooth firmware for the Arduino

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/2335 : Bluetooth: GATT: Remove obsolete flush callback - https://gerrit.zephyrproject.org/r/2334 : drivers/nble: Add buffer pool for

Sure this is true, on a UP system the effect would be to simply disable preemption. I think the semantics are the same regardless of the underlying implementation though, right? Every once in a while

I didn't think zflash was supported any more. I followed https://software.intel.com/en-us/node/605211 and was able to to get my D2000 CRB into a usable state. Henry

Boosting priority of the invoking task may not be what we want to achieve. In case of work_queue (correct me if I am wrong) we have an interrupt handler that offloads the long work to the fiber for

You don't need spinlocks in a 1-CPU system. You're probably thinking of a scheduler lock. Could be done like that too. I introduce a lightweight recursive scheduler lock that is to be used by some