|
Upcoming Event: Zephyr Project: APIs - Tue, 07/07/2020 4:00pm-5:00pm, Please RSVP
#cal-reminder
Reminder: Zephyr Project: APIs
When: Tuesday, 7 July 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC
Where:Microsoft Teams Meeting
An RSVP is requested. Click here to RSVP
Organizer:
Reminder: Zephyr Project: APIs
When: Tuesday, 7 July 2020, 4:00pm to 5:00pm, (GMT+00:00) UTC
Where:Microsoft Teams Meeting
An RSVP is requested. Click here to RSVP
Organizer:
|
By
devel@lists.zephyrproject.org Calendar <devel@...>
·
#7150
·
|
|
Steval drone flight control support
Hi, I've noticed that the steval_fcu001v1 board is supported on Zephyr, however I could not find an example with the flight control software. Does anyone know if any work has been done with regards to
Hi, I've noticed that the steval_fcu001v1 board is supported on Zephyr, however I could not find an example with the flight control software. Does anyone know if any work has been done with regards to
|
By
Brenton Chetty
·
#7149
·
|
|
Re: Post 2.3.0 PR merging
Hi Simon,
Not to my knowledge, no. But perhaps Ioannis or Anas know if it’s also documented elsewhere.
Regarding the “stamp of approval” that was mentioned earlier in the thread, I think we
Hi Simon,
Not to my knowledge, no. But perhaps Ioannis or Anas know if it’s also documented elsewhere.
Regarding the “stamp of approval” that was mentioned earlier in the thread, I think we
|
By
Carles Cufi
·
#7148
·
|
|
API meeting agenda: 2020-07-07
Carles has asked me to stand in for him again in coordinating this week's API telecon.
Topics include:
https://github.com/zephyrproject-rtos/zephyr/pull/26305 adding mode flags to
Carles has asked me to stand in for him again in coordinating this week's API telecon.
Topics include:
https://github.com/zephyrproject-rtos/zephyr/pull/26305 adding mode flags to
|
By
Peter A. Bigot
·
#7147
·
|
|
Re: Post 2.3.0 PR merging
Hi Carles,
OK I see. Since you called out the 2-approver change as a cause of the bottleneck, I'm assuming there is data available on this.
I was looking around for discussion about the decision. The
Hi Carles,
OK I see. Since you called out the 2-approver change as a cause of the bottleneck, I'm assuming there is data available on this.
I was looking around for discussion about the decision. The
|
By
Simon Glass
·
#7146
·
|
|
Re: [Zephyr-users] [Zephyr-devel] Post 2.3.0 PR merging
Agreed. Those who can merge, should take 2 approvals and all other checks as a sign that it is ready to merge, no need for the approval of the person who merges, although a 3rd approval might give the
Agreed. Those who can merge, should take 2 approvals and all other checks as a sign that it is ready to merge, no need for the approval of the person who merges, although a 3rd approval might give the
|
By
Nashif, Anas
·
#7145
·
|
|
Re: Post 2.3.0 PR merging
Hi Charles:
This just my personal opinion on the subject. Two approvals is the right thing to do and what the TSC approved earlier this year.
BUT, if the second +1 is just a rubber stamp
Hi Charles:
This just my personal opinion on the subject. Two approvals is the right thing to do and what the TSC approved earlier this year.
BUT, if the second +1 is just a rubber stamp
|
By
Lawrence King
·
#7144
·
|
|
Re: Post 2.3.0 PR merging
Hi Simon,
A decision like that would need to go through the TSC, and in order to be able to vote we’d need to have clear stats on how many PRs are actually blocked by this policy. I was thinking
Hi Simon,
A decision like that would need to go through the TSC, and in order to be able to vote we’d need to have clear stats on how many PRs are actually blocked by this policy. I was thinking
|
By
Carles Cufi
·
#7143
·
|
|
Re: Post 2.3.0 PR merging
Hi Carles,
Perhaps given the situation this should be reversed?
Regards,
Simon
Hi Carles,
Perhaps given the situation this should be reversed?
Regards,
Simon
|
By
Simon Glass
·
#7142
·
|
|
Re: Backport NRF UART fixes to 1.14.x
#lts
Hi Ryan,
This PR is approved and marked Ready in the Backports project.
This means that it will be bulk-merged with others as soon as the next release in the 1.14.x series is prepared.
If you
Hi Ryan,
This PR is approved and marked Ready in the Backports project.
This means that it will be bulk-merged with others as soon as the next release in the 1.14.x series is prepared.
If you
|
By
Carles Cufi
·
#7141
·
|
|
Backport NRF UART fixes to 1.14.x
#lts
Looking to get this PR merged: https://github.com/zephyrproject-rtos/zephyr/pull/24245
Looking to get this PR merged: https://github.com/zephyrproject-rtos/zephyr/pull/24245
|
By
Ryan Erickson
·
#7140
·
|
|
No reviews on PRs
Hi Zephyr team,
I have had PRs to Zephyr that have been reviewed immediately and got merged rather quickly. Some PRs however are not getting a review although (or because) there are many reviewers
Hi Zephyr team,
I have had PRs to Zephyr that have been reviewed immediately and got merged rather quickly. Some PRs however are not getting a review although (or because) there are many reviewers
|
By
Becker Markus
·
#7139
·
|
|
Re: Measuring LiPo on Adafruit nRF52 Feather
Look at samples/boards/nrf/battery, and boards/arm/thingy52_nrf52832/thingy52_nrf52832.dts which adds the voltage-divider compatible that describes the circuit connected to the ADC input. You'll need
Look at samples/boards/nrf/battery, and boards/arm/thingy52_nrf52832/thingy52_nrf52832.dts which adds the voltage-divider compatible that describes the circuit connected to the ADC input. You'll need
|
By
Peter A. Bigot
·
#7138
·
|
|
Measuring LiPo on Adafruit nRF52 Feather
Hello,
I'm quite new to Zephyr, and I have a question related to the nRF52 Adafruit Feather.
As I understand it, this board gives you the ability to measure the voltage on the connected LiPo battery
Hello,
I'm quite new to Zephyr, and I have a question related to the nRF52 Adafruit Feather.
As I understand it, this board gives you the ability to measure the voltage on the connected LiPo battery
|
By
Tomas McGuinness <tomas@...>
·
#7137
·
|
|
Re: Dev-Review Meeting Agenda Jul 2
Had the wrong link here, should be links to:
https://github.com/zephyrproject-rtos/zephyr/pull/26616
https://github.com/zephyrproject-rtos/zephyr/pull/26388
Had the wrong link here, should be links to:
https://github.com/zephyrproject-rtos/zephyr/pull/26616
https://github.com/zephyrproject-rtos/zephyr/pull/26388
|
By
Kumar Gala
·
#7136
·
|
|
Upcoming Event: Zephyr Project: Dev Meeting - Thu, 07/02/2020 3:00pm-4:00pm, Please RSVP
#cal-reminder
Reminder: Zephyr Project: Dev Meeting
When: Thursday, 2 July 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC
Where:Microsoft Teams Meeting
An RSVP is requested. Click here to RSVP
Organizer:
Reminder: Zephyr Project: Dev Meeting
When: Thursday, 2 July 2020, 3:00pm to 4:00pm, (GMT+00:00) UTC
Where:Microsoft Teams Meeting
An RSVP is requested. Click here to RSVP
Organizer:
|
By
devel@lists.zephyrproject.org Calendar <devel@...>
·
#7135
·
|
|
Re: Dev-Review Meeting Agenda Jun 10
Thanks Marti for sharing!
Thanks Marti for sharing!
|
By
Erwan Gouriou
·
#7134
·
|
|
Dev-Review Meeting Agenda Jul 2
Here’s the agenda topics for this week:
* initial steps towards devicetree-based device definitions and dependency representations [@pabigot]
[
Here’s the agenda topics for this week:
* initial steps towards devicetree-based device definitions and dependency representations [@pabigot]
[
|
By
Kumar Gala
·
#7133
·
|
|
Re: Bluetooth mesh and Central role simultaneously
#bluetoothmesh
#bluetooth
Hi Andreas,
No, I don’t think that combination would make sense. One option I forgot to mention is the bt_mesh_suspend() & bt_mesh_resume() APIs. You could try suspending mesh operations
Hi Andreas,
No, I don’t think that combination would make sense. One option I forgot to mention is the bt_mesh_suspend() & bt_mesh_resume() APIs. You could try suspending mesh operations
|
By
Johan Hedberg
·
#7132
·
|
|
Re: Bluetooth mesh and Central role simultaneously
#bluetoothmesh
#bluetooth
Hi Johan,
thank you very much for your help in that matter.
I am aware of the reduced scanning time for the mesh. It’s just that in my scenario the mesh is running all day long, and
Hi Johan,
thank you very much for your help in that matter.
I am aware of the reduced scanning time for the mesh. It’s just that in my scenario the mesh is running all day long, and
|
By
Andreas
·
#7131
·
|