Hi Michael, Where can I find your patch? I'm interested in it as well.

Hey, In Zephyr’s devicetree, there are two separate concepts when it comes to naming a node with a unique name: label property and node label. Is there a design reason why these two have been

Cancelled: Zephyr Project: Dev Meeting This event has been cancelled. When: Thursday, 20 May 2021 3:00pm to 4:00pm (UTC+00:00) UTC Where: Microsoft Teams Meeting Organizer:

Hi, I have a query on drivers in the zephyr code base in regards to interrupt handling that I am seeking advice on: should a driver in zephyr upon getting an unknown interrupt self-destruct itself,

Cancelled: Zephyr Project: APIs This event has been cancelled. When: Tuesday, 18 May 2021 4:00pm to 5:00pm (UTC+00:00) UTC Where: Microsoft Teams Meeting Organizer:

Hi, I have opened a PR that introduces an important change in the documentation build. We will now enable by default the :member: option in the Doxygen directives. This means that all public members

Zephyr: Toolchain Working Group When: Monday, 17 May 2021 3:00pm to 4:00pm (GMT+00:00) UTC Where: Microsoft Teams Meeting Description: Live meeting minutes:

Reminder: Zephyr: Toolchain Working Group When: Monday, 17 May 2021, 3:00pm to 4:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Hi, In all of our modules, UART 0 is the primary UART. We have 8 boards in Zephyr, so we should plan to enable flow control on all those 8 boards and then add 8 overlays to most sample projects to

Hi Jaime, i've moved flow control to DTS as property already existed (https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/bindings/serial/uart-controller.yaml) so this approach is more generic

Hi, compiler is able to figure out things and remove code that is known not to be executed. Code like this will disapear from the binary: if ( 2 > 3) { foo(); } It can even be more complex like

Hi, We are trying to use the silicon labs thunderboard sense2 SLTB004A device with bluetooth. When we program the device the zephyr beacon sample, we get the following error: * Booting Zephyr OS

Hi Jaime, Jamie Mccrae <Jamie.Mccrae@...> writes: I think we might be talking past each other but I think I'm finally getting what you mean. It does sound like we agree that: -

The main west repository [1] has also renamed its default branch to 'main'. Similar guidance applies if you've got a local clone or

Hi, I am new to zephyr, I am reading the logging subsystem code and find that 'LOG_ERR/LOG_INF/LOG_DBG ..., etc.' will be expanded finally by below MACRO looks like even I disable the logging (not set

Hello all, I'm part of a team that is porting Zephyr to Renesas RX65N processors, and we have encountered a bit of a problem. The GCC toolchain for the processor (available at

Hi Marti, Let's say there is a board (all our boards are Nordic-based so this applies to all of them) which has a UART brought out to a header, the UART might be used for a multitude of things, it

Details for how to rename your fork can be found here: https://github.com/github/renaming

Reminder to all that this change has gone into effect. You may additionally want to make this change in your own GitHub fork of Zephyr. - k

Hi (and +Krzysztof in Cc), "lairdjm via lists.zephyrproject.org" <jamie.mccrae=lairdconnect.com@...> writes: To be clear, this PR is limited to nRF SoCs only, it is not