NEW JIRA items within last 24 hours: 3 [ZEP-205] Fail to enable udp loopback for ipv4 https://jira.zephyrproject.org/browse/ZEP-205 [ZEP-207] Fail to have both ipv6 and ipv4 capability in zephyr https

I apologize if this forum is the wrong place to post this question, I was not sure where else to post. I am attempting to build the zephyr nanokernel with the Galileo board. I am following the steps h

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1544 : qmsi: pinmux: use built-in qmsi driver - https://gerrit.zephyrproject.org/r/1546 : Bluetooth: Kconfig: Split debug selection into

NEW JIRA items within last 24 hours: 1 [ZEP-208] Zephyr's cc2520 driver (together with Zephyr's IP stack) does not handle fragmentation of packets properly https://jira.zephyrproject.org/browse/ZEP-20

Hello All https://jira.zephyrproject.org/browse/ZEP-211 has been entered to track a proposal to remove zephyr-env.sh. <<from the ticket>> Currently we require the user to source the zephyr-env.sh envi

Hi Inaky,

Hi there, We are working on a port to a new ARM SoC family (Nordic nRF5X) and are wondering about a couple of things. There has been some discussion lately on whether to use the ARM CMSIS header files

From: Luiz Augusto von Dentz <luiz.von.dentz(a)intel.com> Following the discussion about the Timer API I decided to prototype the feature in the Bluetooth subsystem: XX:XX:XX:XX:XX:XX (public)> securi

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1595 : doc: show information about documentation current version - https://gerrit.zephyrproject.org/r/1594 : Bluetooth: SMP: Make use of

NEW JIRA items within last 24 hours: 2 [ZEP-210] Zephyr TEE compatibility https://jira.zephyrproject.org/browse/ZEP-210 [ZEP-209] Problem in nano_init.c on qemu_x86 https://jira.zephyrproject.org/brow

[RFC] Zephyr IoT Protocols Problem definition Currently, Zephyr does not support any machine-to-machine protocol (M2M). These protocols were defined for inter-communication between devices or nodes in

Hello all, This is a proposal to add an API for reading, writing and updating internal registers of I2C devices. This API would offer a simpler way of communicating with I2C devices that have internal

In preparation for migrating away from Kconfig-based configuration of devices, make CONFIG_SENSOR_DELAYED_WORK visible to the user during config. Previously, it was only activated when a driver needed

Until now, MCP9808 device configuration was done in Kconfig. This imposed a limit on the number of identical devices the driver could handle (1, in this case). Additionally, Kconfig snippets could not

Update the sample app to describe and support two MCP9808 devices. This is meant to illustrate the new style device configuration. Change-Id: I850c7ac307a6a3932bc02c7586e3d0fc03475152 Signed-off-by: V

Hi Tomasz, This is in reference to https://gerrit.zephyrproject.org/r/#/c/914/ I wanted to discuss on-list some of my concerns, and this really leads into a larger topic on how we should handle changi

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1597 : quark_se: quark_d2000: remove all defines that now come from qmsi - https://gerrit.zephyrproject.org/r/1609 : qmsi: spi: fixed war

NEW JIRA items within last 24 hours: 1 [ZEP-212] "~" not working in build env variables https://jira.zephyrproject.org/browse/ZEP-212 UPDATED JIRA items within last 24 hours: 1 [ZEP-145] no 'make flas

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1629 : grove: use default i2c device set in Kconfig - https://gerrit.zephyrproject.org/r/1628 : i2c: use I2C_X nameing instead of I2CX -

NEW JIRA items within last 24 hours: 1 [ZEP-213] net_set_mac() didn't deal wtih NULL https://jira.zephyrproject.org/browse/ZEP-213 UPDATED JIRA items within last 24 hours: 1 [ZEP-177] Windows build wi