Benjamin Walsh wrote: Does that work? Are pended ARM interrupts really "queued" like that? If you have multiple pending interrupts of the same priority I'd have to believe the order of delivery would

Vinayak Kariappa Chettimada wrote: As has been mentioned in gerrit, there is worry about the portability of a lot of this, which is a mostly 1:1 transcription of an ARM feature as I understand it. In

Liu, Baohong wrote: When PWM is used correctly, this shouldn't make any difference at all because the period will be much, much longer than the underlying clock (which is the whole point). Why bother

It looks like Inaky struggled with this a few months back. Sphinx claims to have fixed it in the bug, no idea if we've done anything to patch it on our end: https://github.com/sphinx-doc/sphinx/issues

Sukumar Ghorai wrote: PHYS_LOAD_ADDR is where the code (and rodata, etc...) goes. Quark SE is an execute-in-place architecture, so that address is mapped directly to the flash space on the chip, there

Mahendravarman Rajarao (RBEI/EAA3) wrote: That just means there's no per-SoC checking of linker memory regions. Clearly there should be, but obviously that doesn't mean that such a file is going to ex

This change is a little experimental. Comments requested. The last patch in the series has the clearest explanation of the justification: we have two printf() formatters in the code base, one for prin

Benjamin Walsh wrote: None whatsoever. As someone just now coming up to speed on Zephyr for the first time, this syntax was among the stranger and more alien things I stumbled on. (And I'll be perfect

I just pushed the following to gerrit, for possible merge sometime in the 1.6 timeframe. It will modify outdir to contain separate subdirectories for each BOARD variant built, so they won't collide in

Inspired by the printf discussion last week and no one's explicit rejection of a quick code-size-reduction patch I threw out, I spent a little more time in the minimal libc printf implementation, find

Some random kibitzing. I'm new, so apologies if some of this has been discussed before: Why a stdio-style mode string that has to be parsed and not a fcntl-style flag word which seems like a better fi