Yeah, but that is not backwards-compatible with the API. And that only works for timers, not the other APIs that take timeouts. Although, that might be irrelevant. Interesting idea. That could be a

Hi Marcus, <marcus.shawcroft@...> wrote: Enable/disable was added as an interface to net_if_up and net_if_down, but since these functions are only supposed to be called from the L2 driver we

Hi, Can anyone add some insight on this issue? The code looks to me as if net_if_up/down() were originally added to provide an enable/disable semantic, but we have BT using them in what appears to

Hello, The SDK has a patched newlib c Library. I'm compiling my own Crosscompiler and I want to ask If it's a official Patch or a Patch made by you? If you made the Patch, can I get it or the Source

Hi Ben, You could also use the full bits and add one additional byte to specify the unit of the number. Timers store their unit together with duration and period. For example k_timer_start(timer,

Option 1) would be ideal for the upcoming WiFi offload devices (like TI CC3220), which do full TCP/IP offload onto a co-processor, essentially bypassing the L2 layer. In that case, there is no need

Hi Marcus, <marcus.shawcroft@...> wrote: Note that the enable/disable semantic was introduced for L2 link detection, which is why it is an L2/LL API. Now from the discussion we had in the IRC

sir i am doing weather forecasting using zephyr OS. i am deploying arduino 101 and BME 280 sensor to collect data for forecasting. i found less resources about the programming part of Zephyr OS in

Glad to see your reply for my message. may i know sir which sector you belongs to in ZEPHYR os development.-- Thank you. Regards, Vishwanath. Reddy

Hi, The network interface patches proposed as a result of this thread have generated a fair amount of discussion both in patch reviews and in IRC. Now would seem like a good time to summarize where

ns or us, you still needed 64-bit timeouts for either, which ended up being the major concern. 64-bit math can be costly: we've seen stack usage increase of 80 bytes on some architectures. Also, I

Hi all I am a contributor to https://github.com/FlowM2M/AwaLWM2M. We've been working recently on integrating this into a number of different platforms and would love for Awa to be a part of the

Regarding reserving upper bits, perhaps think about this the other way around. What is the largest sane microsecond sleep? We need only to reserve enough bits to accommodate that... For example once

While Im not sure Im 100% convinced, having negative numbers just be the number in ticks as it was in the old API should be fine. Im curious though why you went for ns when most system wouldn't be

Hi Mike, When prototyping the new API, I started with timeouts as an int64_t in nanoseconds, to allow the same precision as struct timespec, but without the akwardness of having to create an instance

Hi, I raised https://jira.zephyrproject.org/browse/INF-119 which is currently assigned to Inaky. Cheers /Marcus

+1, is there any action to get them back or should we live with it from now on?

Zephyr Devs, Weve started moving our project from Zephyr 1.5 to Zephyr 1.7. One big change (aside from the really big ones like unified kernel and all that) is that the APIs for timers and others

Hi Maureen, thanks for reply. (...) Yes and I can flash with that version although I get above errors I'm not sure how important is that. Despite working flashing procedure and correctly running

Hi Marcus, <marcus.shawcroft@...> wrote: From a developer with no much expertise into what does TRNG/PRNG really means, myself included, Im not sure how using this terms would improve the