Cancelled: Zephyr Project: Dev Meeting

This event has been cancelled.

When:
Thursday, September 23, 2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@...

Description:

We currently have 19 coverity issues, so please ensure that any issues
assigned to you are fixed in the near term.

https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aopen+is%3Aissue+label%3ACoverity

For any strictly new maintainers, feel free to request to join the
maintainers team on GitHub. Thanks to Erwan for the reminder.

https://github.com/orgs/zephyrproject-rtos/teams/maintainers/members


On Wed, Sep 22, 2021 at 12:56 PM Christopher Friedt
<chrisfriedt@gmail.com> wrote:

Also, I would like to welcome the following new / added maintainers
since v2.6.0.

* Stephanos Ioannidis, C Library, CMSIS-DSP Integration, C++
* Robert Lubos, Networking
* Felipe Neves, Espressif Platforms
* Glauber Maroto Ferreira, Espressif Platforms
* Mulin Chao, Nuvoton_NPCX Platforms
* Jun Lin, Nuvoton_NPCX Platforms
* Wealian Liao, Nuvoton_NPCX Platforms
* Enjia Mai, Intel Platforms (X86)
* Tomasz Bursztyka, Drivers: PTP Clock
* David Leach, NXP Platforms
* Ryan Erickson, Drivers: Modem

Hi everyone!

It's that time of the release cycle, and I would like to invite all
maintainers to make PR's for the v2.7.0 LTS release notes [1].

There have been a number of additions already [2] so thanks to those
who have already made changes. For reference, please have a look at
previous release notes [3].

This release cycle is undoubtedly the largest ever. As such, I expect
that the release notes will be quite extensive, so please ensure that
you have sufficient time to make the necessary changes.

Also, I would like to welcome the following new / added maintainers
since v2.6.0.

* Stephanos Ioannidis, C Library, CMSIS-DSP Integration, C++
* Robert Lubos, Networking
* Felipe Neves, Espressif Platforms
* Glauber Maroto Ferreira, Espressif Platforms
* Mulin Chao, Nuvoton_NPCX Platforms
* Jun Lin, Nuvoton_NPCX Platforms
* Wealian Liao, Nuvoton_NPCX Platforms
* Enjia Mai, Intel Platforms (X86)
* Tomasz Bursztyka, Drivers: PTP Clock
* David Leach, NXP Platforms
* Ryan Erickson, Drivers: Modem

Please excuse me if I have forgotten anyone.

Thank you for all of your contributions!

C

[1] doc/releases/release-notes-2.7.rst
[2] https://docs.zephyrproject.org/latest/releases/release-notes-2.7.html
[3] https://docs.zephyrproject.org/latest/releases/index.html

Reminder: Zephyr Project: APIs

When:
09/21/2021
4:00pm to 5:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

Additional item, as per the Stable API Change procedure:

- RFC: API Change: IPM
- Issue: https://github.com/zephyrproject-rtos/zephyr/issues/38609
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/38523

Carles

On 20/09/2021 22:07, Carles Cufi wrote:

Hi all,
Agenda for tomorrow:
- Pinctrl: Now focusing on #37572 as the single PR to target our efforts
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/37572
- Updates by Gerard and Kumar on the state of the PR
- Discussion, specifically Devicetree layout format: https://github.com/zephyrproject-rtos/zephyr/discussions/35077#discussioncomment-1201394
If you have additional items please let me know.

Hey Carles,
can we talk about https://github.com/zephyrproject-rtos/zephyr/issues/38609 as well?

Thank you,

--
Carlo Caione

Hi all,

Agenda for tomorrow:

- Pinctrl: Now focusing on #37572 as the single PR to target our efforts
- PR: https://github.com/zephyrproject-rtos/zephyr/pull/37572
- Updates by Gerard and Kumar on the state of the PR
- Discussion, specifically Devicetree layout format: https://github.com/zephyrproject-rtos/zephyr/discussions/35077#discussioncomment-1201394

If you have additional items please let me know.

Teams link: https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWU2MjZlYWEtZDcwMi00MWQzLTgwMjEtNDdkYjQwMjBjMmFj%40thread.v2/0?context=%7b%22Tid%22%3a%22af0096d9-700c-411a-b795-b3dd7122bad2%22%2c%22Oid%22%3a%22841a7c92-7816-4faf-9887-5e334e88f6d8%22%7d

https://lists.zephyrproject.org/g/devel/calendar
https://github.com/zephyrproject-rtos/zephyr/projects/18

Minutes:
https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit

Regards,

Carles

Hi,

There is a new SDK 0.13.1 release. This is mainly a bug fix release with the main aspect pulling in fixes for an ARM CVE w/GCC, v8m, and trustzone.

https://nvd.nist.gov/vuln/detail/CVE-2021-35465

Latest version of the SDK can be found here:

https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.13.1

Please download and try things out and report any issues.


• gdb:

• Fix ELF file format support issue on MacOS
• newlib:

• Fixed Xtensa malloc failure issue reported in zephyrproject-rtos/zephyr#38258.
• gcc:

• Pull in patches for Arm-GCC-CVE-2021-35465
• qemu:

• Allow setup of ARC's "virt" board memory size

Thanks to all that contributed fixes and enhancements to this version of the SDK.

- k

Zephyr: Toolchain Working Group

When:
09/20/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: Torsten Rasmussen

Description:

Reminder: Zephyr: Toolchain Working Group

When:
09/20/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: Torsten Rasmussen

An RSVP is requested. Click here to RSVP

Description:

We are pleased to announce Zephyr 2.7.0-rc2 \o/

I'm going to nickname this release "Spoon Boy". That's not in any
official capacity. It just happens to be close to when The Matrix 4
trailer was released.

"Do not try and bend the spoon. That's impossible. Instead... only try
to realize the truth..
There is no spoon.. it is not the spoon that bends, it is only yourself."
-- Spoon Boy, The Matrix, 1999

This is the second release candidate in our stabilization period and
brings several bug-fixes and additional tests. Please see the release
page below for a full list of changes between v2.7.0-rc1 and
v2.7.0-rc2.

https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.7.0-rc2

Just as a reminder, there are currently a disproportionate amount of
low-priority issues. The good news is that we have done very well to
keep on track for high priority and medium priority issues. For anyone
that has a few free cycles, please look at open issues that are
assigned to you and please consider picking off any low-hanging fruit
in the coming week.

I also wanted to say a special thank-you to Maureen Helm for all of
her contributions to Zephyr under the NXP umbrella. We're very
fortunate that Maureen will continue on as a member of the Zephyr
community as Sensor Driver Maintainer and Collaborator on the ARM
architecture.

David Leach is taking over maintainership for NXP from here on, so
thank-you to you as well David.

Lastly, thanks to all who contributed to this release!

C

Minutes are up in the usual place:

https://docs.google.com/document/d/15KUINNj7Re0GQiWYpqKvO5jgDw8oiQv3SGJfNHGaPOU/edit#heading=h.g794p090kv26

There was no time for pinctrl.

"Kumar Gala via lists.zephyrproject.org"
<kumar.gala=linaro.org@lists.zephyrproject.org> writes:

Hi Katsuhiro and Andy,

On Tue, Sep 14, 2021 at 7:52 PM Katsuhiro Suzuki
<katsuhiro@katsuster.net> wrote:

On 2021/09/09 10:41, Yasushi SHOJI wrote:

On Thu, Sep 9, 2021 at 12:01 AM Katsuhiro Suzuki <katsuhiro@katsuster.net> wrote:

On 2021/09/08 16:22, Yasushi SHOJI wrote:

On Wed, Sep 8, 2021 at 10:23 AM Katsuhiro Suzuki <katsuhiro@katsuster.net> wrote:
Why do you `use _current_cpu` at all? `_arch_switch()` or
`arch_switch()` on the main branch takes
both new and old thread handles.

Because to keep consistency for another context switching (by preemption) and
other interrupts.
Only _current_cpu.current is available when an interrupt occurred.

The reason why we set _current to the new thread is that we can't set it after
we switch to the new thread. The newly switched thread will just start
running from
the point it left off. Otherwise, we have to make sure that each and
every arch must
set _current to the new thread in `arch_switch()`.

Hmm... It seems that in CONFIG_USE_SWITCH=n case (ex. aarch32(*)) _current_cpu.current
is updated by software interrupt handler.
(*) arch/arm/core/aarch32/swap_helper.S

So I wonder that why CONFIG_USE_SWITCH=y changed strategy to update current thread.

Ah, OK. I didn't answer your question at all. And I don't have the answer.

Andy, would you mind telling us if you have any comments about the
rationale behind this?

--
yashi

Reminder: Zephyr Project: Dev Meeting

When:
09/16/2021
3:00pm to 4:00pm
(UTC+00:00) UTC

Where:
Microsoft Teams Meeting

Organizer: devel@...

An RSVP is requested. Click here to RSVP

Description:

Hello,
as part of the procedure to request a stable API change, here it is the RFC issue link:

https://github.com/zephyrproject-rtos/zephyr/issues/38609

Ciao!

--
Carlo Caione

ipc_service: Introduce RPMsg multi-core backend:
- https://github.com/zephyrproject-rtos/zephyr/pull/38328

drivers: regulator: convert to gpio_dt_spec
- https://github.com/zephyrproject-rtos/zephyr/pull/37689

Pinctrl - devicetree if we feel like it...

Plus anything anyone else has.

- k

I have two Nrf52840 boards. One of them is flashed with open Thread Coap server and the other with Coap client. I have been trying to pair this two boards for a while, but could not succeed, I do not know what I am doing wrong. Please help.