Perhaps we should note that interpretation 1 is the "right" one in the sense that this is what the current implementations of the API currently approximate to. I also view interpretation #2 is only

Hello, We have a problem in the UART (and UART driver) API very akin to the proverbial half-empty vs half-full glass problem. So, there're 2 interrupt testing predicates: * uart_irq_tx_ready() *

Hello,

Hi, I am a day old since I started in Zephyr and from Arduino background. Could you please help with an example how to read from UART ports which are from

Hello, It's fair to say that we're seeing the need to better test various error handling paths in Zephyr, for example, in networking code. This is commonly handled with fault injection. I grepped

Hello, This report is quite overdue, and I hoped to have sent it weeks ago, as the initial implementation of all the basic functions were done long ago. But I wanted to back it with automated easily

Hello Jukka,

Andrew, This is only possible if you're a member of the organization. Right now, as far as I can tell, people are mostly contributors to the "zephyr" repository there. This is in the pipeline to be

Marti, That's indeed a known limitation. In this case, it might be sufficient to zero out the struct hawkbit_ctl_res struct, and then just NULL-check _links.cancelAction.href or

Github appears to have a feature where you can have notification emails to sent to different email addresses depending on the ‘organization’ that owns a particular project. Under Personal Settings

Hit send too soon. ...uire changes to the Zephyr API. Here is the reference on the JSON I am trying to parse, for the hawkBit device management

Hi, I am trying to convert an application to use the Zephyr JSON library in lib/json from jsmn [1], and have run into an issue that I think will req [1] https://github.com/zserge/jsmn

Hi, We are now on github and PRs are flowing in, CI is operational as expected and we are getting used to the new flow. Thank you for all who helped make this happen. Now, we have been on

Hi Kevin, there is no driver for ESP6288 in Zephyr. Patches are welcome to fix this situation. Cheers, Jukka

Hi Paul, Thanks for pushing this, we definitely have an issue with the rcv wnd handling. I like this better than an application manually calling a special function to do the trick like what was

Hi all, I just submitted a simple HTTP client API for review at https://github. com/zephyrproject-rtos/zephyr/pull/50 The API is very simple providing following functions: * http_client_send_req():

Wonderful; glad to hear it! Marti

Marti, Yes, those will be enabled on github as well, emails should start flowing in during this week. Anas

Hi Anas, Thanks for the information. I read through the emails on this and the Contribution Guide on the Zephyr GitHub wiki, which was clear. One thing I don't see is whether the daily Gerrit digest

Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: I hope you guys are aware of CONTRIBUTING.md: https://github.com/blog/1184-contributing-guidelines , so hope the content will be moved there