The 1.6 tag was created on the branch. Starting with 1.6 we create a branch during the stabilisation period and continue development on master or the next release. This is the current model also descr

Hi, Sometime a go we used to have the board documentation in the tree, since then we move those to the wiki and right now there is some kind of disconnect between the boards we have in the source tree

Hi, Here is a quick proposal for improving documentation of samples and integrating them into the online documentation available on zephyrproject.org. The RFC is also tracked in Jira under https://jir

Here is a snippet: uint32_t version = sys_kernel_version_get(); printk("Zephyr version %d.%d.%d ", SYS_KERNEL_VER_MAJOR(version), SYS_KERNEL_VER_MINOR(version), SYS_KERNEL_VER_PATCHLEVEL(version)); Th

Hi, I am pleased to announce that we have tagged Zephyr 1.6.0, merge window for 1.7 is now open. Thanks to all who participated and made this release happen, this was a true collaborative effort up to

Hi, Hoping this would be the last release candidate before the final 1.6 release. Here is the change log since the last release: Anas Nashif (3): release-notes: cleanup entries release notes: update h

Hi, We had an issue in gerrit where a change targeting the net branch was pushed to master branch for review by mistake. The change was merged into master pulling all its dependencies from the net/ br

Hi, We have tagged Zephyr 1.6 rc2, below are the changes since the first release candidate. In summary, we have the following changes: - Fixes for issues discovered by coverity - Documentation changes

Hi, If you are submitting fixes or changes to 1.6, please submit them to master branch and add a topic that starts with 1.6, for example: # git push origin HEAD:refs/for/master/1.6-fix-foo-bar If a va

Hi, As announced a few days, we have tagged the first release candidate of 1.6 (v1.6.0-rc1) and on schedule to release 1.6 end of this month. We have lots of changes and good stuff since 1.5, the deta

You are trying to push an abandoned patch? https://gerrit.zephyrproject.org/r/#/c/6207/ Sent: Friday, November 11, 2016 11:51 AM To: devel(a)lists.zephyrproject.org Subject: [devel] Can't push to Gerr

Hi, We are one week away from the planned 1.6-rc1 release. Please make sure you have submitted all new features and bug fixes into Gerrit by now and take into consideration the time needed for review.

# make ram_report or # make rom_report For an analysis of all objects in the final binary Anas Sent: Wednesday, November 2, 2016 2:10 PM To: devel(a)lists.zephyrproject.org Subject: [devel] Reg: Memor

Marcus, Do you have a list of the code you mention below? Anas

Yossi, Looks ok, I am fine with this. Can you please put this into a JIRA story and if you have code already, submit it to gerrit. You also need to submit a sample backend and testcases or samples to

This is not Zephyr related, it all depends on the bootloader you are using. QMSI 1.1 had a bootloader that booted the sensor subsystem directly, not sure if this is still the case in recent releases t

Hi, Vinicius can say more, but there was an early POC on top of the new stack a few weeks back, the plan is to move to new IP stack for 1.6 and ASAP. https://jira.zephyrproject.org/browse/ZEP-818 cove

Eitan,, In principle I agree we need to support additional backends, but I do not think this fits in how it is being done in sys_log.h. I propose to extend syslog to support custom backends without ha

Ok, there is a JIRA about board/soc structure documentation already and it happens to be assigned to me, I will address this ASAP, this might help you with the issue below. Anas

Hi, Some time ago the TSC discussed APIs in general and it was agreed that we need to revisit the APIs as we have them right when there is critical mass of architecture and board support and I think w