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

Thank you for letting me know. I will send a patch to fix it. -------- Daniel Leung

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 4 [ZEP-178] Port Zephyr to Altera Max10 (Nios 2 CPU) https://jira.zephyrproject.org/browse/ZEP-178 [ZEP-53]

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1383 : Bluetooth: Add support for confirming incoming JustWorks pairing - https://gerrit.zephyrproject.org/r/1393 : gcc: add __weak

Hi Daniel, I didn't catch this at first, but the patch causes a problem for the Grove LCD driver (not sure if this problem is also present for other drivers). The way it was written, the Grove LCD

Hi, To establish relationships between Jira items and gerrit requests and to enhance traceability of changes we have a system in place that handles the cross-reference and creates the necessary links

Hey Jason,

NEW JIRA items within last 24 hours: 1 [ZEP-199] Zephyr driver model is undocumented https://jira.zephyrproject.org/browse/ZEP-199 UPDATED JIRA items within last 24 hours: 2 [ZEP-70] Users

I would suggest starting with RFC, as it may be good to have it implemented in the Zephyr OS kernel: If we enable NANO_TIMER_CALLBACK config option, we start a fiber that sleeps on all the

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1364 : doc: sphinx conf: use env var in sphinx doc version - https://gerrit.zephyrproject.org/r/1381 : tests: Pend microkernel tasks

Hi Dmitriy, <dmitriy.korovkin(a)windriver.com> wrote: Yes, it is actually what we already have in IP which maintain a fiber to execute the callbacks but the API is based on contiki etimers which is

Hi Maureen, I'm very glad to hear this. First I was interested for the onboard peripherals, like the RGB-LED and the accelerometer. But these were only for tests. Originally I bought this board for

Hi Daniel, Are there plans for Zephyr OS to run on STM32F401 (Nucleo-64) boards? Thanks, Jason

Problem Statement: Shrink binary size by doing driver_api assignment at compile/link time. Problem Description: For some drivers, the assignment of driver_api is unconditionally done. This is

In other words, the idea of several fibers does not work for you, I see. Ok, now it gets clearer. You are asking for a nanokernel timer API that executes a registered callback when it expires. I do

I don't remember exactly. One of the them was some renaming of either pinmux or gpio functions/structures.

I think we shouldn't change our existing APIs at all. They should be treated as a contract. Someone who builds code against 1.0 should be able to do so against later versions until we make a conscious

I see. So the method in the RFC is to assist in diagnosis or notification of critical errors.

Changing APIs.

Ramesh, in a production release, there should not be any non-critical errors at device initialization (hence "production"). In a production environment, the null-returning can be used as a mechanism