On Wed, 17 Aug 2016 17:26:39 +0300 Paul Sokolovsky <Paul.Sokolovsky(a)linaro.org> wrote: [] > So, I'm not sure what the exact issue is. I may imagine following > might happen: > > 1. There was a

Hi. My first post on this list so would like to say that this project seems very promising and is something that I have been waiting for. I wanted to get involved so I dusted of a STM32F3 discovery

NEW JIRA items within last 24 hours: 1 [ZEP-714] I2C fails to write/read the fourth slave among operation of multi-slaves https://jira.zephyrproject.org/browse/ZEP-714 UPDATED JIRA items within

"Flavio Santes" <flavio.santes(a)intel.com> wrote: Yes, thanks, I meant for Ethernet support in FRDM-K64F which I have on my hands now. [] I've made first pass of changes

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4137 : samples/net: Remove call to unref routine when net_send returns >= 0 - https://gerrit.zephyrproject.org/r/4152 : Bluetooth:

Amir, All commits need to pass Jenkins, so you should make the changes and organise the commits in a way that keeps Jenkins happy all the way. Thanks, Anas

Hi, Following Ramesh and Ku-Lang's feedbacks we have split the changes to multiple small patches(instead of the original delivery). Note: Due to the fact that the drivers changes depends on the

See https://gerrit.zephyrproject.org/r/4160 for the maintainers. Anas

Which reminds me to ask... who _are_ the ARM maintainers and how do we find out such things given that the MAINTAINERS file in the source tree is somewhat deficient in coverage? -- Tixy

Hello See also https://jira.zephyrproject.org/browse/ZEP-188 Agree There is support for real hardware,

No objection from me. Sounds reasonable to me as well. I'd like to hear from the ARM maintainers to get their opinion too. Cheers, Ben

NEW JIRA items within last 24 hours: 2 [ZEP-713] Implement preemptible regular IRQs on ARC https://jira.zephyrproject.org/browse/ZEP-713 [ZEP-711] I2c: fails to write with mode fast plus

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4127 : WDT: remote duplicated wdt clock enable code - https://gerrit.zephyrproject.org/r/4136 : Bluetooth: Fix race condition between

Hello, Taking a chance, I'd like to start with drawing attention to https://jira.zephyrproject.org/browse/ZEP-687 "docs: Subsystems/Networking section is almost empty". Zephyr networking information

Hello Rohit, Rohit Grover <Rohit.Grover(a)arm.com> wrote: There's already TCP support in samples/net/echo_server , you just need to build it with CONFIG_NETWORKING_WITH_TCP=y . While waiting

Sounds reasonable to me. (I'm new around here though, so don't count that as anything other than a random opinion ;-) My main thought was that boards/SoCs select a CPU type which then selects the

It's definitely not an option to always build choices in at compile time for each board, as there could be thousands or even millions of instances of a particular target board in the IoT space. Being

Did not expect this to generate such a big discussion. Here is a use case in addition to what was mentioned in the thread below. Think of this API as a helper API for higher lever features and not a

TIxy, I am thinking either, CPU_HAS_BASEPRI or ARCH_HAS_BASEPRI. I also want to add an ARCH_ARMV6, V7 etc to handle architecture specific code. We still need the more specific CPU_CORTEX_M0PLUS, 3,