On Sat, 1 Apr 2017 14:16:12 +0300 Paul Sokolovsky <Paul.Sokolovsky@...> wrote: [] > as long as fifo would allow me to wait until it becomes non-empty This appears to be the hardest part. I see

Hello, Motivation: BSD Sockets API work. I already have code like: + // TODO: k_fifo accessor for this? + struct net_buf *last_buf = (struct net_buf*)sys_slist_peek_tail(&socket->recv_q.data_q); to pe

Hello, This matter already came up in patch reviews and during BSD Sockets discussion, and I think it's worth to have a dedicated discussion on it. So, currently there're 2 problems: 1. Zephyr header

Hello Marcus, Marcus Shawcroft <marcus.shawcroft@...> wrote: Well, we do have a particular implementation - Zephyr RTOS, which defines a lot of traits/constraints (for example, Zephyr is current

Hello Daniel, Daniel Thompson <daniel.thompson@...> wrote: If we're talking about the same things, then there's no "imposing of additional requirements". And the opposite of "integration nightm

Hello Luiz Augusto,

Hello, This is old news, and there was a related drama at Linux kernel community long ago. So, with uber-advanced compilers, like GCC 5/6 (Zephyr SDK 0.9 uses 6.2.0), at a certain optimization level (

Hello Luiz Augusto,

Hello Leandro, Leandro Pereira <leandro.pereira@...> wrote: Sounds like an interesting idea, thanks for sharing, I'll keep it in mind and will look into it at later stage. Right, that's exactly

Hello Gil, Thanks for the reply, please let me both agree and not agree to some points. Gil Pitney <gil.pitney@...> wrote: I'm on their side, but such application developers will quickly see th

Michael, "Goldman, Michael" <michael.goldman@...> wrote: Glad to hear it worked. And we really need more eyes on Zephyr networking, so any report is appreciated, and we need to know what issues

"Goldman, Michael" <michael.goldman@...> wrote: I get such messages when I don't have ./loop-socat.sh running (in another terminal window), so you may want to check you follow https://www.zephyr

Hello, "Goldman, Michael" <michael.goldman@...> wrote: What BOARD? I believe I tested it on Sat with qemu_x86 and saw IPv6 pings (but didn't try actual data echoing). []

Hello Jukka,

On Mon, 27 Mar 2017 13:19:16 +0200 Tomasz Bursztyka <tomasz.bursztyka@...> wrote: [] > That's the thing: there won't be any other wrappers. > There is Zephyr's net stack with net_context,

Hello Tomasz, Tomasz Bursztyka <tomasz.bursztyka@...> wrote: Please note that these names belong to LIBC namespace, not Zephyr namespace. So, in our case it's up to Newlib to define them i

Hello Sterling, Thanks for the prompt feedback! "Sterling Hughes" <sterling@...> wrote: Thanks for MyNewt references on the matter, I'll finally have a good excuse to look into again (the time

Hello, Support for BSD Sockets API in Zephyr is one of the frequently asked features from different parties. Possibility of such support was a topic of discussions at the recent OpenIoT Summit Portlan

Paul Sokolovsky <Paul.Sokolovsky@...> wrote: Well, too early. I do build against Zephyr, I use its configuration and includes, but my 3rd party project doesn't use Zephyr *Makefiles*. So, __ZEP

Marcus Shawcroft <marcus.shawcroft@...> wrote: Cool, thanks for replies! I grepped include/* for anything like that, I checked predefined macros in gcc. Who'd new I should grep Makefiles too ;-)