Hi Bogdan, My thoughts inline... <bogdan.m.davidoaia(a)intel.com> wrote: Indeed, on some platforms the use of double will come with a very significant code size, performance and power implication. Int

Hi, We have two crypto libraries in /ext, tinycrypt and mbedtls. Can someone help me understand: - What is the plan / strategy here, are we moving the code base from one to the other. - Do we expect b

Hi, Looking at an issue Carles and others have been chasing it appears that the ARM irq_lock() implementation is broken. The absence of a memory clobber allows the compiler to reorder it relative to o

Adding the various maintainers CC... Your thoughts/views on this would be much appreciated... <marcus.shawcroft(a)gmail.com> wrote:

Hi, The current include/gpio.h interface allows for basic configuration of a gpio pin. The nRF5 hardware supports three different configurable drive strengths on each pin, independently for 0 and 1 ou

Hi Chuck, Configuring GPIO_DS_0_STANDARD | GPIO_DS_1_DISCONNECT is essentially setting up a pin as an open collector output. The pin is driven to 0, but a 1 output is left high impedance. I can imagin

An example of the scenario above would be an nrf5 i2c driver that needs to use the nrf5 gpio driver to put the two pins used for clock and data into an open collector mode. Cheers /Marcus

Hi Tomasz, <tomasz.bursztyka(a)linux.intel.com> wrote: The three modes standard, high, disconnected are mutually exclusive hence the proposal to represent them as three values encoded in a two bit fie

<tomasz.bursztyka(a)linux.intel.com> wrote: Understood. _low_ _high_ does make sense. Cheers /Marcus

<tomasz.bursztyka(a)linux.intel.com> wrote: Hi Tomasz, do you want to take ethernet driver changes on the net branch aswell, or should those go to master ? Cheers /Marcus

On 29 November 2016 at 21:54, Davidoaia, Bogdan M <bogdan.m.davidoaia(a)intel.com> wrote: Hi Bodan, > If we want to define specific value types for each channel type, then we might as well have the sa

Re-send with updated email address for Bogdan...

Hi Bodan, I was just checking that the plan had not changed. Thanks for the update. Cheers /Marcus

Hi! I noticed this review fly by: https://gerrit.zephyrproject.org/r/#/c/9982/ Which essentially adjusts a Kconfig to have an SPI driver Kconfig explicitly select a GPIO driver when it needs the GPIO

Hi, [Second attempt at responding, my arm email address seems to have triggered a moderator approval, sorry about the duplication for those of you that got a direct reply.] This is because the code is

Since the type is 'uint32_t' rather than 'unsigned' the correct specifier is: PRIu32 e.g. #include <stdint.h> printf("blah %" PRIu32 " more blah", v); Cheers /Marcus

That would be my fault, my example above is missing: #include <inttypes.h> Cheers /Marcus

We will likely find either immediately, or with future additions to /ext that each blob of third party code does something different: - Some will use %u for uint32_t - Some will use %lu for uint32_t -

This is not a choice between alternatives. There are two separate decisions here: 1) Do we align minimal C with newlib in order to have consistent breakage in /ext irrespective of the users choice bet

How easily can we feed different -W options to the /ext part of the tree, or is that painful ? Cheers /Marcus