If we focus only on bugfixes and security then there is no concern
My coment was mostly related to new boards,drivers and architectures which
usually have spread comits
On Wed, 12 Feb 2025, 09:27 raiden00pl, wrote:
> Nathan, that's not what I mean.Look at this comment from Alin and
> discussio
Here goes my vote with too :-P
On Tue, Feb 11, 2025 at 12:37 AM Tomek CEDRO wrote:
> 1. In Contributing Guidelines we are adding additional section for
> Reviewers in order to provide complementary set of rules that should
> filter out breaking code as much as possible also on our side.
+1: This
If we a gree to provide SBOM for our releases:
a source SBOM (json file) file will be provided together with the download
link and will provide insight on our fill source code and license
a build SBOM (json file) will be generated after a build containing only
the code that was compiled on that dev
On Wed, Feb 12, 2025 at 11:37 AM Tomek CEDRO wrote:
> 18. Pull Requests should be as small as possible and focused on only
> one functional change. Different functional changes should be provided
> in separate Pull Requests. Remember that breaking changes are not
> welcome. Pull Requests must not
> 18. Pull Requests should be as small as possible and focused on only
> one functional change. Different functional changes should be provided
> in separate Pull Requests. Remember that breaking changes are not
> welcome. Pull Requests must not break overall build, runtime, and
> compatibility, es
I am redirecting questions from Takashi to this thread :-)
On Wed, Feb 12, 2025 at 6:45 AM Takashi Yamamoto
wrote:
> On Tue, Feb 11, 2025 at 8:37 AM Tomek CEDRO wrote:
> > 7. Each git commit message must consist of topic, description, and
> > signature, which are mandatory, or change is auto-rej
Hello
I have an absolutely neutral position on this issue.
We dont use sboms.
but maybe in some future we might be required to provide it. However I
dont have any clue of that happening in the near or mid future.
What does it look like? It's just a static file somewhere, right?
Sebastien
O
Lets add these two points to vote that came out of the discussion and
see the reaction.
This vote is to see what subjects we do agree already and what needs
update / clarification :-) Where are all +1 we can implement already,
where is at least one -1 that needs fix, where is 0 we may clarify
some
On Wed, Feb 12, 2025 at 2:13 PM Tiago Medicci Serrano
wrote:
> Hi!
> Tomek, there is an important missing point about 19 (that is part of my
> proposal):
>
> 19. "Lazy consensus" is a situation where PR is auto-merged into the
> > upstream when not enough reviews are done in predefined time (i.e.
Hi Yashvi,
Please send the dump of this crash, using it you can find where the code is
crashing.
BR,
Alan
On Wed, Feb 12, 2025 at 2:51 AM 175 yashvi shah
wrote:
> Hello,
>
> I am attempting to retrieve data from a BMI270 sensor on an STM32H7 board.
>
> However, when using the I2C scanner, a p
Hi!
Tomek, there is an important missing point about 19 (that is part of my
proposal):
19. "Lazy consensus" is a situation where PR is auto-merged into the
> upstream when not enough reviews are done in predefined time (i.e.
> there are no minimum required positive reviews within two weeks time).
On Wed, Feb 12, 2025 at 12:11 PM Alin Jerpelea wrote:
> If we a gree to provide SBOM for our releases:
> a source SBOM (json file) file will be provided together with the download
> link and will provide insight on our fill source code and license
> a build SBOM (json file) will be generated after
On Wed, Feb 12, 2025 at 6:45 AM Takashi Yamamoto
wrote:
> On Tue, Feb 11, 2025 at 8:37 AM Tomek CEDRO wrote:
> > 7. Each git commit message must consist of topic, description, and
> > signature, which are mandatory, or change is auto-rejected until fixed
> > / updated. Topic consists of functiona
Nathan, that's not what I mean.Look at this comment from Alin and discussion
below it: https://github.com/apache/nuttx/pull/15789#issuecomment-2648017787
wt., 11 lut 2025 o 21:33 Nathan Hartman
napisał(a):
> There will be regular releases as well and if I am understanding correctly,
> all PRs t
On Tue, Feb 11, 2025 at 10:54 AM Alin Jerpelea wrote:
> Hi all,
> I have been working on a SBOM implementation for our project and I think
> that we are getting ready top provide both source and build SBOMS like
> Zephyt.
> What is your opinion about SBOM?
> Would an SBOM help you and your company
Yes
Details of error
dump_assert_info: Current Version: NuttX 12.8.0 1828d09b2a-dirty Feb 12
2025 0m
dump_assert_info: Assertion failed panic: at file: :0 task:
process: K5
up_dump_register: R0: 4000541c R1: R2: 0048 R3:
0001
up_dump_register: R4: R5: R6: 000
Hi Yashvi,
You can enable the debug symbols to inspect where your code is crashing
(the positions at LR: 0800d3b7 PC: 0800dcbe)
Enable it in your menuconfig:
Build Setup ---> Debug Options ---> [*] Generate Debug Symbols
Then flash the new image and run:
arm-none-eabi-addr2line -e nuttx 0800
Hello,
Fine, I have no opposition, and yes it could become actually useful.
As Tomek noticed, we also need to document what it is so it has an
impact on many docs, and also on the website.
Sebastien
On 12/02/2025 12:11, Alin Jerpelea wrote:
If we a gree to provide SBOM for our releases:
a
Hi!
Thanks, Tomek ;)
So, rewriting 19:
*19.* A PR may be *eligible* to be merged under the concept of *Lazy
consensus* with the following conditions:
- It affects only a single chip or board (no
kernel/libs/upper-half drivers etc);
- It implements a new feature (or app) that
I have created an initial RN2XX3 driver here:
https://github.com/apache/nuttx/pull/15828
The design was based on some suggestions received on the mailing list earlier
in the year. I haven't added quite all of
the `ioctl` commands I would like yet, and I want to add some Kconfig options,
but I a
Hi Yashvi,
Please describe the issue you are facing. BTW, did the i2c scan find your
BMI270?
BR,
Alan
On Wed, Feb 12, 2025 at 2:41 PM 175 yashvi shah
wrote:
> But
>
> I’m having a little trouble finding the BMI270 option in the application
> configuration examples.
>
> Thank you!
>
> On W
Hi,
Again, Sebastien, read it *carefully*. It seems you are not willing to do
it.
It doesn't bypass anything:
- either the submitter still cares and will yell at people to get it
> approved
* My proposal says explicitly about this:*
The PR's author should:
> - After a week (
Yes, I successfully completed the I2C scanner.
After achieving success with I2C, I need to retrieve data from the BMI270.
For that, I have done all the necessary configurations, and everything
seems perfect. However, when I try to enable the BMI270 in the application
configuration -> "Examples," t
Hello
I enabled the sensortest in sensor drive <- testing<- application
configuration..
But in ls/dev
Uorb is not available+ imu0 is visible
On Thu, Feb 13, 2025, 1:00 AM Alan C. Assis wrote:
> Hi Tim,
>
> It came from PX4 and how it is used for our sensors.
>
> BR,
>
> Alan
>
> On Wed, F
Ah - so something you choose to use or not? But still we'll have
"traditional" drivers for new sensors as they're added?
On 12/02/2025 19:29, Alan C. Assis wrote:
Hi Tim,
It came from PX4 and how it is used for our sensors.
BR,
Alan
On Wed, Feb 12, 2025 at 4:21 PM Tim Hardisty
wrote:
Is
I am not able to understand can you describe it briefly?
Thank you!
On Thu, Feb 13, 2025, 1:35 AM Tim Hardisty wrote:
> Ah - so something you choose to use or not? But still we'll have
> "traditional" drivers for new sensors as they're added?
>
> On 12/02/2025 19:29, Alan C. Assis wrote:
> > Hi
Hi Tim,
It came from PX4 and how it is used for our sensors.
BR,
Alan
On Wed, Feb 12, 2025 at 4:21 PM Tim Hardisty
wrote:
> Is uORB really just a PX4 thing? Not NuttX? Or did NuttX adopt uORB too
> and I missed it?
>
> Just curious :-)
>
> On 12/02/2025 18:51, Alan C. Assis wrote:
> > Hi Yash
Yes, we still have char driver sensors and uorb sensors
On Wed, Feb 12, 2025 at 5:05 PM Tim Hardisty
wrote:
> Ah - so something you choose to use or not? But still we'll have
> "traditional" drivers for new sensors as they're added?
>
> On 12/02/2025 19:29, Alan C. Assis wrote:
> > Hi Tim,
> >
>
Hello,
By applying this, I was able to successfully execute the I2C scanner.
Thank you!
On Wed, Feb 12, 2025, 9:16 PM Alan C. Assis wrote:
> Hi Yashvi,
>
> You can enable the debug symbols to inspect where your code is crashing
> (the positions at LR: 0800d3b7 PC: 0800dcbe)
>
> Enable it in y
But
I’m having a little trouble finding the BMI270 option in the application
configuration examples.
Thank you!
On Wed, Feb 12, 2025, 11:05 PM 175 yashvi shah wrote:
>
>
> Hello,
>
> By applying this, I was able to successfully execute the I2C scanner.
>
> Thank you!
>
> On Wed, Feb 12, 20
The goal is not to automatically merge PR, but only to avoid that some PRs
that don't reach the maximum number of reviews be allowed to be merged.
Typically, those who are most eager to impose new rules are not the same as
those who are subject to them!
BR,
Alan
On Wed, Feb 12, 2025 at 2:5
Thanks Lwazi and Peter. By examining the data in the NuttX binary I have
tentatively concluded that the binary, as stored as an MCUboot signed
bootable image:
* Has the 32 byte MCUboot header. This contains the address in RAM
that the entire image in the flash slot, minus the 32 byte header
Lwazi,
My bad, but you could build Nuttx for armv7-a and disassemble its vector
table to figure it out.
Try configuring Nuttx for qemu-armv7a:nsh and build the image. Then
using addr2line you can determine where the source for the vector table
is via "addr2line -e nuttx 0x0" which returns
"
This "lazy consensus" seems hot topic, lets just gather the feedback
votes for now to see how many +1 / 0 / -1 are out there, then we will
discuss the details, everyone may have their own reasons and for sure
we can express them freely here :-)
Thanks :-)
Tomek
On Wed, Feb 12, 2025 at 7:21 PM Ti
On Wed, Feb 12, 2025 at 7:45 PM Tiago Medicci Serrano
wrote:
> I would like to propose another topic:
> * Enhancing on-demand paging algorithm on NuttX:
> - It already has a rudimentary on-demand paging algorithm that allows
> mapping the `data` memory on-demand (
> https://nuttx.apache.org/doc
Sorry I'm taking a break from GSoC this year :-) Last GSoC was horribly
stressful, this year I'll focus on NuttX CI.
I compiled some GSoC Tips here: https://github.com/apache/nuttx/issues/11957
Lup
On Thu, Feb 13, 2025 at 8:05 AM Tomek CEDRO wrote:
> On Wed, Feb 12, 2025 at 7:45 PM Tiago Medic
On Wed, 12 Feb 2025 at 13:10, Tim Hardisty wrote:
> Thanks Lwazi and Peter. By examining the data in the NuttX binary I have
> tentatively concluded that the binary, as stored as an MCUboot signed
> bootable image:
>
> * Has the 32 byte MCUboot header. This contains the address in RAM
> tha
Is uORB really just a PX4 thing? Not NuttX? Or did NuttX adopt uORB too
and I missed it?
Just curious :-)
On 12/02/2025 18:51, Alan C. Assis wrote:
Hi Yashvi,
BMI270 uses uORB, you need to use sensortest (CONFIG_SYSTEM_SENSORTEST)
Just verify if the sensor was created correctly at /dev/uorb/
Again, I will vote against this. Not that it matters if a majority wants
to approve it.
This is a bypass of all other rules we're trying to enforce.
If such situation arise, there are two cases:
- either the submitter still cares and will yell at people to get it
approved
- either it will b
I would like to propose another topic:
* Enhancing on-demand paging algorithm on NuttX:
- It already has a rudimentary on-demand paging algorithm that allows
mapping the `data` memory on-demand (
https://nuttx.apache.org/docs/latest/components/paging.html#kernel-build-implementation).
However, i
Hi Yashvi,
BMI270 uses uORB, you need to use sensortest (CONFIG_SYSTEM_SENSORTEST)
Just verify if the sensor was created correctly at /dev/uorb/
BR,
Alan
On Wed, Feb 12, 2025 at 3:23 PM 175 yashvi shah
wrote:
> Yes, I successfully completed the I2C scanner.
>
> After achieving success with I
On Wed, Feb 12, 2025 at 5:15 PM Tiago Medicci Serrano
wrote:
> So, rewriting 19:
>
> *19.* A PR may be *eligible* to be merged under the concept of *Lazy
> consensus* with the following conditions:
> - It affects only a single chip or board (no
> kernel/libs/upper-half drivers etc);
>
42 matches
Mail list logo
