Hi Joakim, I have not measured this. At the moment the IP stack is configured to have separate TX and RX buffers. So in minimal configuration there would be one TX and one RX buffer vs. in Contiki

What I was proposing in my last reply, too keep things simple, is one Kconfig option to enable/disable handling of error codes by init functions. If it's disabled, nothing is handled automatically and

Looks like it. You want to do the implementation yourself Jukka ?

Sounds good, but we need to do it in away that keeps APIs compatible I guess. Anas

Thanks for documenting this but I don't think forcing people to use git-review is the right approach. It worked for us before in many other projects, why is this different and why can't I use vanilla

Makes sense but why not tell the compiler the truth about the type?

How about something like this: diff --git a/kernel/nanokernel/device.c b/kernel/nanokernel/device.c index f86f95f..82774c4 100644 --- a/kernel/nanokernel/device.c +++ b/kernel/nanokernel/device.c @@

Hi Anas, Quoting Nashif, Anas (2016-02-19 14:07:36) Yes, I agree. I'm not a gerrit expert but from I could understand, this is related to the 'forge author' settings from submitter rights. I'm CCing

Ugh, you're right, it's a nano_thread_id_t.

We're just returning a thread ID when we start a fiber now, you can ignore it. I don't see an issue here...

You are right, this will not break existing code. Nevertheless, we should track such API changes and document them in release notes. Anas >

Sure.

This should work. We need to rework some of the drivers as they make the driver_api assignment unconditionally. ---------- Daniel Leung

Hi, I had set up all the dev libaries, SDK and downloaded required files ( https://www.zephyrproject.org/doc/board/galileo.html ). but under $ZEPHYR_BASE directory when I did make BOARD=galileo it

Hi, I had set up all the dev libaries, SDK and downloaded required files ( https://www.zephyrproject.org/doc/board/galileo.html ). but under $ZEPHYR_BASE directory when I did make BOARD=galileo it

Hi, I had set up all the dev libaries, SDK and downloaded required files ( https://www.zephyrproject.org/doc/board/galileo.html ). but under $ZEPHYR_BASE directory when I did make BOARD=galileo it

Hi, You need to go into an application directory and build in the application directory, for example: $ cd samples/hello_world/nanokernel $ make BOARD=galileo Regards, Anas

That should be fine. So the kernel decision to abort will be based on a "fatal" error return from any of the device's init function. We still need to decide what does "abort" mean for kernel. It

Why not create a dedicated status field in device object? Additionally we can provide an API to query status of devices. This will help query status of devices it does not bind to.

Dear Zephyr development team, following the instructions in your Getting Started Guide [1], I tried to run source zephyr-env.sh in my zsh 5.2, but get: zephyr-env.sh:2: = not found With my