On Wed, Apr 16, 2025 at 3:37 PM Carlos Sanchez
wrote:
> > > I was going to propose another global CAN change, removing the 1000
> > > factor from bitrate thus making bitrate calls use units in Hz instead
> > > of kHz, so we can discuss that and (if agreed) I make the change on
> > > the same PR t
Hello everyone,
I am starting a new drone project which I am hoping to use NuttX for, and as
part of the project I am looking for NuttX
supported boards that include WiFi support. I was thinking, it might be useful
for the NuttX documentation to make use
of a tag system to easily search for feat
> > While testing this, I think I have discovered a small mistake on my
> > previous, Nuttx-side PR, which slipped by me and by revision: "ret"
> > might be used uninitialized now because I removed the assignment on
> > stm32_fdcan_sock:1976
> Yes, please make a PR to fix that!! When it's ready, p
I really like that idea!
I am not super familiar with the layering of Kconfig feature options, but I am
of the understanding that a board Kconfig
file might not list itself all the features it has. So the parser would have to
determine which chip the board is using,
and by extension which featur
So this would be like a cross-vendor parametric search for boards... cool!
It would also be helpful if this kind of parametric search could be part of
the NuttX website. This way, visitors who hear about NuttX can see the
great number of supported boards and choose one for their project. They
migh
On Wed, Apr 16, 2025 at 3:53 PM Peter van der Perk
wrote:
> can_ioctl_data_s is in a 32-bit union.
>
> https://github.com/apache/nuttx/blob/40c6af6dec0d769ac57f69e89709f9d6310ee0c6/include/net/if.h#L299
> Making it 64-bit would break that union.
>
>
but lifr_ifru doesn't require its member size t
+1 for compatibility with Linux.
śr., 16 kwi 2025 o 10:04 Xiang Xiao napisał(a):
> On Wed, Apr 16, 2025 at 3:53 PM Peter van der Perk <
> peter.vanderp...@nxp.com>
> wrote:
>
> > can_ioctl_data_s is in a 32-bit union.
> >
> >
> https://github.com/apache/nuttx/blob/40c6af6dec0d769ac57f69e89709f9d
can_ioctl_data_s is in a 32-bit union.
https://github.com/apache/nuttx/blob/40c6af6dec0d769ac57f69e89709f9d6310ee0c6/include/net/if.h#L299
Making it 64-bit would break that union.
Hence back then it was chosen to use kHz instead.
Yours sincerely,
Peter van der Perk
-Original Message-
Fr
Hi Peter,
> can_ioctl_data_s is in a 32-bit union.
> https://github.com/apache/nuttx/blob/40c6af6dec0d769ac57f69e89709f9d6310ee0c6/include/net/if.h#L299
> Making it 64-bit would break that union.
Maybe I am missing something. AFAIU can_ioctl_data_s is already 64-bit
(it includes 4 uint16_t member
I have created the PRs:
nuttx: https://github.com/apache/nuttx/pull/16225
nuttx-apps: https://github.com/apache/nuttx-apps/pull/3061
BR
Carlos
On Wed, Apr 16, 2025 at 10:07 AM raiden00pl wrote:
> +1 for compatibility with Linux.
>
> śr., 16 kwi 2025 o 10:04 Xiang Xiao
> napisał(a):
>
> > On
> > I was going to propose another global CAN change, removing the 1000
> > factor from bitrate thus making bitrate calls use units in Hz instead
> > of kHz, so we can discuss that and (if agreed) I make the change on
> > the same PR to avoid creating so a tiny one.
> What's the unit used on Linux
11 matches
Mail list logo
