Sorry for the late notice, but canceled this weeks (Jan 7th) dev-review meeting as there are no PRs flagged for discussion - k

Cancelled: Zephyr Project: Dev Meeting This event has been cancelled. When: Thursday, 7 January 2021 4:00pm to 5:00pm (UTC+00:00) UTC Where: Microsoft Teams Meeting Organizer:

Reminder: Zephyr Project: APIs When: Tuesday, 5 January 2021, 5:00pm to 6:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Hi Steven, Your PRs do not modify existing APIs or add any new ones, from what I can tell after a quick look. You can either wait for reviews, or bring those up at the dev-review meeting on

Question? Would my two driver addition PR be in this meeting? If not could you direct me to the appropriate call/place? drivers: sensor: mcp9600: Added driver and sample for mcp9600 area:

Reminder: Zephyr: Networking Forum When: Tuesday, 5 January 2021, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

One extra item to the agenda: - drivers: eeprom: mark the EEPROM API as stable - PR: https://github.com/zephyrproject-rtos/zephyr/pull/31076

Hi all, I am cancelling todays (5 Jan) Network forum meeting as there is no topics to discuss. Cheers, Jukka

Hi all, Agenda for today, taken from the Triage column in the project. - API to correlate system time with external time sources and translate uptime to wall-clock time - PR:

Hi All, I'm working on adding support for the X-NUCLEO-BNRG2A1 ST shield. This would extend the implementation of X-NUCLEO-IDB05A1. The BNRG2A1 shield uses a newer version of the BlueNRG SPI

Hi all, There is a network forum meeting tomorrow Tue 5 Jan at 8AM PST / 17.00 CET. Currently the agenda is empty, so if there is anything network related topics you want to discuss, please let me

Hi all, I have submitted a PR to mark the Zephyr EEPROM API as stable for the upcoming Zephyr v2.5.0 release. The EEPROM API was introduced in Zephyr v2.1.0 and has not seen any changes

Hello, I am looking at using the Zephyr Bluetooth Object Transfer Service but my use case also has need for write support. I am happy to add the support but wanted to ask if anyone is already

Hello Maureen-san, I have one question. Who is most suitable person if we want to discuss or merge RISC-V subsystem and RISC-V related drivers (not core kernel)? It seems that mainly Nashif and

Hi, Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.0 NOTE: In some cases changes are required to utilize SDK 0.12.0 with Zephyr (for

Reminder: Zephyr Project: Dev Meeting When: Thursday, 17 December 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

Here’s the agenda topics for this week: * start switching to feature-specific binding model - https://github.com/zephyrproject-rtos/zephyr/pull/30594 replace device define macros with

Reminder: Zephyr Project: APIs When: Tuesday, 15 December 2020, 5:00pm to 6:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer:

One additional item if time permits: - subsystem: task_wdt: Implement software watchdog suitable for multiple threads - PR: https://github.com/zephyrproject-rtos/zephyr/pull/28947

Hi all, Agenda for today. Note that this will be the last API meeting of 2020. The following one will take place in January 5th, 2021. - drivers: can: Rework can_configure API and zcan_frame - PR: