Typically the RAM region is defined to be the size of the available RAM on the target board. You are in one of two scenarios: - The size of RAM defined by the build is too small, there is actually mor

What I did for Nios II (which is a soft-CPU that runs on Altera FPGAs) is to define each different Nios II configuration as a different soc in the Zephyr build. So for example I have the "nios2f-zephy

+1000 Andrew

Hi Carles, Can you submit your contribution to our Gerrit server? https://nexus.zephyrproject.org/content/sites/site/org.zephyrproject.zephyr/latest/contribute/gerrit.html Regards, Andrew

I don't see a problem with replacing the existing definition in the minimal libc with the corrected version above. Can you send a patch against lib/libc/minimal/include/stddef.h? Andrew

Hello All, New RC tagged. Thanks to everyone for your contributions! Anas Nashif (1): MAINTAINERS: add ARM and ARC architecture maintainers Andrew Boie (19): samples: hello_world: build for sanitychec

I've written a patch to clean up and add a layer of abstraction for how the arch/x86/ code talks to the interrupt controller code. There are all internal APIs not used by apps. https://gerrit.zephyrpr

Thanks Niheer. wrt item #2, my current understanding is that all internel kernel interfaces are prefixed with '_'. Andrew

They were exposed to the application level. They both were concerned with installing interrupt handlers dynamically at runtime. The preferred approach nowadays is to configure interrupts statically at

I am not too deeply familiar with ARM arch code. Ben Walsh would be the person to talk to. I believe he gets back from sabbatical today although it may take him some time to get through all his email.

________________________________ Sent: Thursday, July 28, 2016 5:33 PM To: Boie, Andrew P; devel(a)lists.zephyrproject.org Subject: RE: deprecation policy No not at this time. There is one reference t

Do we have a concrete policy on deprecated APIs? A while back we agreed to deprecate the dynamic IRQ / exception APIs, and task irq APIs, and they all have been marked with __deprecated. The change th

Suggestion: instead of different APIs for getting the ID and Version, how about one API which takes an enumerated type to select which data to retrieve? For example something like: enum soc_metadata_t

I've made some changes to how custom exception handlers are registered on X86 to hopefully make them much easier to deal with. https://gerrit.zephyrproject.org/r/#/c/3450/ Review/comments appreciated

OK. I do have to ask though, what makes Zephyr an attractive target for this platform? Is it unable to run Linux? Andrew ________________________________ Sent: Tuesday, July 26, 2016 12:50 AM To: deve

I think we might be interested in taking this. Can you rebase your patch series onto the Zephyr trunk and send to our Gerrit review server? What kind of testing has been done so far? Andrew __________

I found a longstanding issue with EOI and nested interrupts, where after EOI, there was a race between the next interrupt on the same line coming in, and the IRQ code popping context, resulting in the

Since we've established we should do this at build time, why not make this a Kconfig or some other #define instead of adding C code which will add to the footprint? Andrew

Scalability across HW with the same binary is not one of Zephyr's goals. We really try to do everything at build time to make the OS as small and fast as possible. This is why dynamic interrupts were