Interesting, some parts of the documentation gave me the (wrong?) impression that a BOARD allowed some level of variation and configuration at build time: https://docs.zephyrproject.org/latest/guides/

Looks like https://lists.zephyrproject.org/g/devel/topic/61321118

https://docs.zephyrproject.org/latest/search.html?q=mesh+onoff From: <devel@...> on behalf of Brett Preston <bpreston@...> Date: Wednesday, 18 December 2019 at 13:2

Run-time aspects aside, I (naively?) believe using a different language enforces a much cleaner and maintainable separation between generic code and hardware specific configuration. The Linux kernel h

I think it's the same object-oriented pattern than the Linux one described in more detail at: https://lwn.net/Articles/446317/

Extremely useful workaround: https://github.com/zephyrproject-rtos/zephyr/commits/v1.14-branch \-> https://github.com/zephyrproject-rtos/zephyr/pull/19639 \->https://builds.zephyrproject.org/zephyrpro

It should but might not be enough because ufw is just a user interface. Use "ip[6]tables -L" to verify the actual state.

#nrf52840 #samples

One of those jobs that everyone needs but no one wants to do? PS: versioning plus a bit more https://docs.zephyrproject.org/latest/guides/west/why.html

It's still not clear to me what you're looking for but maybe this git command will help: git log --decorate --no-walk --oneline $(git tag -l v1.14*) upstream/v1.14-branch 5ad3f4a6930d (tag: v1.14.1-rc

Shippable's "rich" UI affects not just accessibility but also any user trying to perform simple things like searching for some specific error message across all 5 shards or (let's go crazy) across dif

On Linux the script zephyrproject/tools/ci-tools/scripts/check_compliance.py -c commit_range checks all that for you. I also got the script running on Windows too once with a couple hacks. Marc From:

#samples #microbit #robot

There's a violation of the "Least Astonishment" principle but it's not with the '%s'. The '%s' traditionally refers to the type of the argument only, it says nothing about memory management. I don't t

Such a "sharp tool" should at least not look exactly like the slow but safe version used absolutely everywhere else. http://www.catb.org/~esr/writings/taouu/html/ch01s03.html#rule-surprise On the same

Good guess. Anas found the bug (commas) and fixed it at https://github.com/zephyrproject-rtos/zephyr/commit/af3f81ef04bccd0b959 Curious how Anas debugged this because I just found this user who put a

Hi, While github's features should really work as expected to save confusion and everyone's time, I hope this "under-review" risk is very small because I would expect every reviewer to... review the l

[duplicate message cause the web interface doesn't seem to support cross-posting] I don't know about the github side, however I just found and fixed a number of issues in the Zephyr script that checks

You may need one extra level of quotation, see --extra-args CMAKE_C_FLAGS example and sanitycheck pointer in https://github.com/zephyrproject-rtos/zephyr/pull/14593/files "test/determinism.sh" http://

In this example, passing either 1, --test, or 2. --subtest, or 3. both seems to make no difference; in all 3 cases the same, complete kernel.fifo.poll set gets run: ./scripts/sanitycheck -v -v \ --tes

As I wrote above "make htmldocs" works for me, this PR is actually an htmldocs demo. It would point at the difference(s) between my environment and CI = the vast majority of CI failures when testing l

There's an actual (and draft) PR now in case anyone else is interested in following this: https://github.com/zephyrproject-rtos/zephyr/pull/13805 Still just a demo. Off the list now. From: <devel@list