Hello Piotr,

"Nashif, Anas" <anas.nashif@...> wrote: Well, just as you tried to present the issues in the net stack from the different sides, just the same I try to present an extended perspective of the iss

Tomasz Bursztyka <tomasz.bursztyka@...> wrote: [] Right, I had the same idea, mentioned in the other mails. [] I posted https://github.com/zephyrproject-rtos/zephyr/pull/1507 showing how t

Hello Anas, "Nashif, Anas" <anas.nashif@...> wrote: We can approach it from another side. Let me present some cases I faced (some of them based on other users' feedback), and you'll try to guess

Jukka Rissanen <jukka.rissanen@...> wrote: It's that there're too many options, and need for a particular option or an effect of some option is hard to anticipate, and if one didn't, an ap

Hello Andrew, "Boie, Andrew P" <andrew.p.boie@...> wrote: Thanks for support. I'm not much familiar with logging in other susbystems, so wanted to start with a humble, pilot proposal first, thou

Hello, I more the once mentioned the issue that Zephyr IP networking is very hard to configure. It almost impossible to configure a slightly-above-trivial app from scratch: something won't work with i

Hello, "Li, Jun R" <jun.r.li@...> wrote: Well, that's not specific enough. It's not enough to define a config option "in a Kconfig file somewhere" for it to be actually available in Zephyr build

Hello, Andrzej Kaczmarek <andrzej.kaczmarek@...> wrote: ENOTSUP is your friend (except Linux thinks it should be EPERM, see below). POSIX has it: http://pubs.opengroup.org/onlinepubs/7908799/x

Hello,

Hello Andrzej, Andrzej Kaczmarek <andrzej.kaczmarek@...> wrote: Well, NFFS is a *flash* filesystem, it's expected that it would require more specific underlying device type than a generic FS l

Hello Maciej, Maciej Dębski <maciej.debski@...> wrote: *All* tests fail sooner or later, with or without a reason. (As Murphy would add, non-tests fail sooner or later too.) If you're sure it's

Hello Jonas, Jonas Pfaff <jonas.pfaff@...> wrote: I'd think the good approach is to fit it into an existing subsystem instead of creating new entities. So indeed, a sensor subsystem seems like a

Hello, David Brown <david.brown@...> wrote: I recently hit a case when I needed to run Zephyr SDK on 32-bit system and of course, it was a rather unpleasant surprise to remember that I can't. I

Hello Andrew, "Boie, Andrew P" <andrew.p.boie@...> wrote: It would be interesting to ask someone who posted a first bug on Github why they did that. But I'd imagine the answer would be "The proj

Hello Daniel, Daniel Thompson <daniel.thompson@...> wrote: Heh, removing all I wrote in the unsent version of this reply, indeed, it's my bug. It's the "for" played bad trick on me, seeing its

Hello, Previously, there already were examples of the compiler fanciness: https://lists.zephyrproject.org/pipermail/zephyr-devel/2017-March/007426.html Here's another one, which is a pure bug. Given c

Hello, Some people started to use Github's project issue tracker at https://github.com/zephyrproject-rtos/zephyr to file routine issues (*not* epics or user stories) - for example, regression reports

Hello Yannis, Yannis Damigos <giannis.damigos@...> wrote: [] Thanks for confirming this. I by now also submitted a Github report, it borders on a bug that a review author can't dismiss their own

Hello, I spotted a following issue: if I gave negative ("change requested") review (or just the same, positive review), I don't seem to be able to change it back to "no review". For example, if I look