about DMA API updates proposal
Hake Huang
Hi All,
I am working on enable NXP EDMA drivers to Zephyr DMA framework, and I have two DMA API changes need to discussion. 1. https://github.com/zephyrproject-rtos/zephyr/pull/28895 in this PR, I add chain_link by using the dest_chaining_en(Major) and source_chaining_en(minor).
Slack topic discussion is here
Can this topic be scheduled in next API meeting? Thanks.
|
|
Re: Dev-Review Meeting Agenda Feb 25
Bolivar, Marti
Minutes from today's meeting are posted here:
https://docs.google.com/document/d/15KUINNj7Re0GQiWYpqKvO5jgDw8oiQv3SGJfNHGaPOU/edit#heading=h.xuqvp7a5nn9s
|
|
Zephyr Project: Dev Meeting - Thu, 02/25/2021 4:00pm-5:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: Dev Meeting When: Thursday, 25 February 2021, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: devel@... Description: ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
Dev-Review Meeting Agenda Feb 25
Kumar Gala
Here’s the agenda topics for this week:
drivers: move sdmmc controller drivers to drivers/sdmmc (Johann Fischer) - https://github.com/zephyrproject-rtos/zephyr/pull/32605 usb: add common HID definitions header (Johann Fischer) - https://github.com/zephyrproject-rtos/zephyr/pull/32582 Revert practice of removing devicetree labels (Peter - https://github.com/zephyrproject-rtos/zephyr/issues/32608 https://github.com/zephyrproject-rtos/zephyr/labels/dev-review * Any topics anyone else has. - k
|
|
Updated Event: Zephyr Project: LTS schedule and scope meeting - Tuesday, 2 March 2021
#cal-invite
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr Project: LTS schedule and scope meeting When: Where: Organizer: devel@... An RSVP is requested. Click here to RSVP Description: We will hold a special one-off meeting to discuss the schedule and scope of the next LTS release. ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
Zephyr Project: LTS schedule and scope meeting - Tue, 02/23/2021 5:00pm-7:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: LTS schedule and scope meeting When: Tuesday, 23 February 2021, 5:00pm to 7:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: devel@... Description: We will hold a special one-off meeting to discuss the schedule and scope of the next LTS release. ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
Re: LTS schedule and scope meeting on Tuesday, 23rd February
Nashif, Anas
Hi,
There is nothing absurd about discussing this topic at any time. This is a major release with significant impact, and we should be able to make the assessment and have a judgment call if we are ready to release something or not, at any time. Ideally, progress should have been tracked and assessed earlier, I agree, but better late than never.
Unfortunately, you are just looking at one aspect of what LTS is, which happens to be in the name (LTS) and disregarding everything else. The project has defined what LTS is and its significance, both in the charter and in discussions leading to the first LTS which set the ground for future LTS releases. The “old slides” are what the project agreed on and are not some random opinions by someone. The following is how LTS was defined:
“Long Term Support” is not a release criterion, it is a release characteristic that can’t be accomplished or done if you do not have the following 2 criteria points: stable and mature APIs and expanded testing and coverage. The last point about being certifiable derives from mature APIs and expanded testing with additional items that overall serve the quality and maturity of the project and sets the ground for additional work that can be done on top of an LTS release which is part of the project charter, which I would not disregard so easily.
Right now, 2 options are being considered:
There might be other options here, but ideally, we should avoid having multiple variants of zephyr that are maintained for a long period of time. There is a lot of overhead associated with that.
Anas
From:
<devel@...> on behalf of "Peter A. Bigot" <pab@...>
As an active Zephyr contributor for over two years, speaking as an self-employed contractor and not for anybody that funds some of those contributions, I would like to provide a perspective on the LTS issue.
On 2/18/21 4:19 AM, Carles Cufi via lists.zephyrproject.org wrote:
Hi all,As you probably know, on Tuesdays we have two regularly scheduled meetings:- API meeting (17:00 UTC)- Bug triage and Release Readiness meeting (18:00 UTC)This week however, we will hold a special one-off meeting to discuss the schedule and scope of the next LTS release.The meeting will be open to everyone and will last two hours.When: Tuesday, 23rd February, 17:00 UTC (18:00 CET, 12PM EST, 11AM CST, 9AM PST)Where: 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%7dThanks,Carles
|
|
Re: LTS schedule and scope meeting on Tuesday, 23rd February
Peter A. Bigot
As an active Zephyr contributor for over two years, speaking as
an self-employed contractor and not for anybody that funds some of
those contributions, I would like to provide a perspective on the
LTS issue.
toggle quoted messageShow quoted text
LTS1 (1.14.0) was released 2019-04-06. The published date for LTS2 release is 2021-05-28. That LTS2 was expected by the middle of this year cannot be considered a surprise. I find it absurd that we are now, three months before that release, discussing whether it will occur on schedule, and what it will be. Regardless of what the Zephyr charter or old slide decks contain, the term LTS is widely understood to mean "long term support": a reasonably well-tested release with a commitment to provide over several years scheduled updates that fix important security or functional problems. Companies plan product releases with the expectation that the frameworks they're depending on will stabilize and be available in a supported release at roughly the promised date. I recognize that many features that Zephyr member companies had intended to be in LTS2 aren't ready. But that's a problem for those companies, and shouldn't be made into one for other Zephyr stakeholders. A decision to not release 2.6 this spring/summer as LTS2 and support it as promised would abrogate the agreement Zephyr has with its users, particularly affecting smaller companies and individuals who are not project members, don't have any vote in this question, and may not even be aware that it's being discussed. My recommendation is: Proceed with 2.6 LTS2 as promised. Direct short-term planning effort toward scaling down and documenting expectations for this release, and to addressing significant known shortfalls in existing features if that can be done without breaking things. Announce soon exactly what will be in 2.6, and release it on schedule as an LTS. Then go back and figure out what went wrong and how to address the process gaps that led to this situation. Peter
On 2/18/21 4:19 AM, Carles Cufi via
lists.zephyrproject.org wrote:
Hi all, As you probably know, on Tuesdays we have two regularly scheduled meetings: - API meeting (17:00 UTC) - Bug triage and Release Readiness meeting (18:00 UTC) This week however, we will hold a special one-off meeting to discuss the schedule and scope of the next LTS release. The meeting will be open to everyone and will last two hours. When: Tuesday, 23rd February, 17:00 UTC (18:00 CET, 12PM EST, 11AM CST, 9AM PST) Where: 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 Thanks, Carles
|
|
Zephyr: Toolchain Working Group - Mon, 02/22/2021
#cal-notice
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr: Toolchain Working Group When: Where: Description: Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r
________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
|
|
Zephyr: Toolchain Working Group - Mon, 02/22/2021 4:00pm-5:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr: Toolchain Working Group When: Monday, 22 February 2021, 4:00pm to 5:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: Torsten Rasmussen Description: Live meeting minutes: https://docs.google.com/document/d/1IQKBK-GcJNZG0O9QArqYfvb6Huk5xHscN-XIGEZr-z8/edit#heading=h.x36xe8bnwr9r
________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 682 738 030#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
|
|
#custom_board Ti MSP432E4XX platform support.
#custom_board
psanyi@...
Hello
I have added support for Ti MSP432E4XX platform. For the moment it provides basic board support, but more will come. :) To build the project it was necessary to add platform support also for hal_ti Regards
|
|
Bluetooth: HCI RPMsg on nRF5340
#bluetooth
#hci
renkai@...
Hi,
I have two questions about HCI RPMsg: 1. If I have nRF5340DK, what's the <board name> I can use to build the firmware? nrf5340dk_nrf5340? nrf5340dk_nrf5340_cpuapp? nrf5340dk_nrf5340_cpunet? 2. I found that "#define HCI_RPMSG_ISO 0x05" was added on main.c, does it mean that this sample code support the HCI commands related to Bluetooth LE Isochronous Channels? Kai
|
|
SDK 0.12.3 Release
Kumar Gala
Hi,
Latest version of the SDK can be found here: https://github.com/zephyrproject-rtos/sdk-ng/releases/tag/v0.12.3 Please download and try things out and report any issues. * Backport GCC 10.2+ (ie, changes that would be in GCC 10.3) for Arm for fixes associated with Cortex-M55 - k
|
|
Updated Event: Zephyr Project: LTS schedule and scope meeting - Tuesday, 23 February 2021
#cal-invite
devel@lists.zephyrproject.org Calendar <noreply@...>
Zephyr Project: LTS schedule and scope meeting When: Where: Organizer: devel@... An RSVP is requested. Click here to RSVP Description: We will hold a special one-off meeting to discuss the schedule and scope of the next LTS release. ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
LTS schedule and scope meeting on Tuesday, 23rd February
Carles Cufi
Hi all,
As you probably know, on Tuesdays we have two regularly scheduled meetings: - API meeting (17:00 UTC) - Bug triage and Release Readiness meeting (18:00 UTC) This week however, we will hold a special one-off meeting to discuss the schedule and scope of the next LTS release. The meeting will be open to everyone and will last two hours. When: Tuesday, 23rd February, 17:00 UTC (18:00 CET, 12PM EST, 11AM CST, 9AM PST) Where: 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 Thanks, Carles
|
|
Cancelled Event: Zephyr Project: Dev Meeting - Thursday, 18 February 2021
#cal-cancelled
devel@lists.zephyrproject.org Calendar <noreply@...>
Cancelled: Zephyr Project: Dev Meeting This event has been cancelled. When: Where: Organizer: devel@... Description: ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 483 314 739#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
Zephyr Project: APIs - Tue, 02/16/2021 5:00pm-6:00pm, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 16 February 2021, 5:00pm to 6:00pm, (GMT+00:00) UTC Where:Microsoft Teams Meeting An RSVP is requested. Click here to RSVP Organizer: devel@... Description: Meeting decisions/discussions in their respective PRs, tracked here: https://github.com/zephyrproject-rtos/zephyr/projects/18 ________________________________________________________________________________
+1 321-558-6518 United States, Orlando (Toll)
Conference ID: 317 990 129#
Local numbers | Reset PIN | Learn more about Teams | Meeting options
________________________________________________________________________________
|
|
API meeting: agenda
Carles Cufi
Hi all,
Agenda for today: - Go through the project and triage - Set goals for 2.6 - Any additional topics that might be raised 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://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion https://github.com/zephyrproject-rtos/zephyr/projects/18 https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit Regards, Carles
|
|
Zephyr 2.5.0 released, merge window is now open.
Nashif, Anas
Hi, We are pleased to announce the release of Zephyr RTOS version 2.5.0!
Major enhancements with this release include:
processor implementation.
The detailed release notes can be found here:
https://github.com/zephyrproject-rtos/zephyr/releases/tag/zephyr-v2.5.0
The next release, v2.6.0, is scheduled for May 28th, 2021. The merge window is now open.
Thank you to everyone that contributed features, documentation, testing, infrastructure, and bug fixes!
Regards, Anas
|
|
Zephyr 2.5.0-rc4 tagged / Last Call for release notes
Nashif, Anas
Hi, The fourth release candidate for Zephyr v2.5.0 has been tagged (v2.5.0-rc4). This is planned to be the last release candidate. Only blocker issues will be considered.
The merge window for features and enhancements remains closed until v2.5.0 is released.
This is the last call for release notes, in case you notice something missing, please let us know or submit a change to:
https://github.com/zephyrproject-rtos/zephyr/blob/master/doc/releases/release-notes-2.5.rst
More information about bugs counts and real-time tracking of bug counts can be found here: https://testing.zephyrproject.org/issues/zephyrproject-rtos/zephyr/index.html
Testing Zephyr master branch during the stabilization period is also requested; please test the code base and file bug reports so they can be addressed before the release deadline.
All changes since 2.5.0-rc3 can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.5.0-rc4
More details about Zephyr releases can found on the pages below: https://docs.zephyrproject.org/latest/development_process/release_process.html
You may continue to send Pull Requests for new features in order to gather feedback early or collaborate with others, but the release team would like to encourage everyone to focus on bugfixes and documentation improvements to the largest extent possible, so that we can release v2.5.0 on time and in the best shape possible. If you have a feature or enhancement you would like to submit to the TSC, please tag the Pull Request with the "TSC" label, make sure it is approved and passing CI, and attend the next TSC meeting.
Thanks, Anas
|
|