Hi all, We are ITE and we want to submit our chip support to the upstream. Our business partners have ever mentioned it in your weekly process meeting. He says you are compleatedly OK eventhough our

Hi all, We currently have 170+ Pull Requests that pass CI but require one or more approvals in order to be merged, in part due to the fact that we have increased the minimum number of approvals

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

I see no toolchain meeting today but one next week, on the 18th, which is what Torsten intended:

I still see the old calendar entry and not the new one. Thomas Den 2020-06-11 kl. 15:45, skrev Danny Ørndrup (DAOR) via lists.zephyrproject.org: --

Hi Carles, Thanks. Strange, that is not reflected in my calendar, which is linked to the zephyr calendar, but that must be a problem on my end though. Regards, Danny

Hi Danny, The calendar was updated earlier today. Carles

Hello, on my nRF52 board I am planning to have a Bluetooth mesh node running and then eventually (e.g. on button press) create a connection to a smartphone (nRF52 in Central, smartphone in Peripheral

Hi Torsten, Could you update the calendar? If not already done. I believe that many will miss out, if the calendar does not reflect the rescheduling of the meeting. Regards, Danny

Hi Ryan, This is still TBD, I will soon call a meeting to decide on this year’s qualification plans. Thanks, Carles

Today’s meeting has been postponed to 18 June. Sorry for the late notice. See you all in a weeks’ time from now. Best regards Torsten T. Rasmussen Live meeting

"Bolivar, Marti via lists.zephyrproject.org" <marti.bolivar=nordicsemi.no@...> writes: The meeting has moved to a new Teams home and I've been told the wiki is up to date, for

It seems like TSC moved to a new Teams meeting; will this be moving, too? "Kumar Gala via lists.zephyrproject.org" <kumar.gala=linaro.org@...> writes:

Here’s the agenda topics for this week: * struct device - plans for 2.4: https://github.com/zephyrproject-rtos/zephyr/issues/22941 https://github.com/zephyrproject-rtos/zephyr/issues/26072

Hi Paul, Sure, let me post here for everyone's reference: On Feb 2020 (https://docs.google.com/document/d/1xiO721JwqW_H_BpGMOJ4PY3vLVy7nxW2fhy841nsP10/edit#heading=h.7ckwoo5xq75a) Zephyr TSC approved

Are there any plans for Zephyr 2.3 to be BT SIG certified for host, controller, or profile (mesh) subsystems?

Hello Ioannis, "Glaropoulos, Ioannis" <Ioannis.Glaropoulos@...> wrote: Thanks for the notification, Ioannis. I might have missed the discussion and decision-making behind this change, can

Hello, There's no need to open an issue. The alias should be named eeprom-0 in a DTS file, aliases { eeprom-0 = ...; }; but needs to be eeprom_0 (i.e. "lowercase-and-underscores" form) in

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

Hi Carles, thanks, I managed like this: / { aliases { eeprom_0 = &eeprom0; }; }; but eeprom_0 is not a valid alias: dtlib.DTError: /aliases: alias property name 'eeprom_0' should