Hello I am in charge of development for the configuration tool mentioned by Vlad. Our tool aims to help developers both for Zephyr and Linux manage device configurations on build time and ACPI,

I've left the rest of the structure and the helper that uses it below and trimmed the rest of the code for clarity. There is nothing about these that is sensor- or device-specific (well, besides the

Signed-off-by: Jukka Rissanen <jukka.rissanen(a)linux.intel.com> --- Hi, current network application APIs in Zephyr are synchronous and a bit of awkward to use in TCP. Because of these things, I

Hi, Zephyr v1.3.0-rc1 has been tagged. The merge window for new features is now closed. The target date for the 1.3.0 release is end of this week. Below is the list of changes since

Leading underscore is reserved by the kernel for internal global symbols.

^^^^^^^ DEFINE ? SENSOR_ prefix ?

Were you envisionning having this as a "device" type of fiber, or were you thinking having this as an even more generic concept ? -- Benjamin Walsh, SMTS Wind River Rocket www.windriver.com Zephyr

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 0 CLOSED JIRA items within last 24 hours: 0 RESOLVED JIRA items within last 24 hours: 0

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1683 : doc: Remove references to Bluetooth from Networking - https://gerrit.zephyrproject.org/r/1682 : gpio: Fix returning codes -

Adding Tony, he can explain more about the tool. Thanks, Vlad

Hi Ben, <benjamin.walsh(a)windriver.com> wrote: Well that was what I mentioned that the use of nano_timer is very limited, if you look at the unit test you will quickly realize how hard it is to use

Hi, I prefer building zephyr the linux kernel way, which is (what i am used too): $ make ARCH=arm CROSS_COMPILE=arm-none-eabi- ZEPHYR_BASE=~/workspace/zephyr menuconfig $ make ARCH=arm

Hello, Please read carefully: (1) http://www.intel.com/content/www/us/en/embedded/products/galileo/galileo-g2-datasheet.html (2)

Don't you think it would be confusing for a user that we have two timer APIs and a timeout API ?

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 0 CLOSED JIRA items within last 24 hours: 0 RESOLVED JIRA items within last 24 hours: 0

Ok, so then throwing the memory at a struct and play around with it will not be a good option. I guess most of this memory will then be accessed by strict APIs and not as plain bytes. It sounds like

Hi Joakim, the fragments will be individual small buffers with possibly some link level layer space reserved before the actual data. This way it is possible to avoid memory copy in lower network

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/1639 : doc: fix typo IMACU -> IAMCU - https://gerrit.zephyrproject.org/r/1638 : build: generate error if board is not found -

Hi! Quick question without a deep dive in the code. Is it intended to create consecutive fragments to allow using the packet/network memory directly (e.g. to will a fragmentet buffer look the same

Hi All, I just uploaded net_buf fragmentation support to gerrit. https://gerrit.zephyrproject.org/r/#/c/1648/ The fragmentation support allows the network stack to use smaller buffer fragments to