Re: Please recommend NuttX

2024-07-11 Thread Alan C. Assis
I wasn't expecting anything different from ARM:

https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644/3

This is why I think RISC-V will win!

BR,

Alan

On Wed, Jul 10, 2024 at 6:34 PM Alan C. Assis  wrote:

> Dear NuttXers,
>
> Just as you were talking about NuttX awareness, see that:
>
> https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644
>
> They recommended FreeRTOS and Zephyr (no surprise here), but no reference
> to NuttX.
>
> Please help us to get awareness about NuttX.
>
> If you don't want to write a post, just click Like on my post, it will be
> enough.
>
> Best wishes,
>
> Alan
>


Re: Please recommend NuttX

2024-07-11 Thread Gábor Kiss-Vámosi
At least you can add a link to NuttX in your comment.

Gabor

Alan C. Assis  ezt írta (időpont: 2024. júl. 11., Cs,
11:20):

> I wasn't expecting anything different from ARM:
>
> https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644/3
>
> This is why I think RISC-V will win!
>
> BR,
>
> Alan
>
> On Wed, Jul 10, 2024 at 6:34 PM Alan C. Assis  wrote:
>
> > Dear NuttXers,
> >
> > Just as you were talking about NuttX awareness, see that:
> >
> > https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644
> >
> > They recommended FreeRTOS and Zephyr (no surprise here), but no reference
> > to NuttX.
> >
> > Please help us to get awareness about NuttX.
> >
> > If you don't want to write a post, just click Like on my post, it will be
> > enough.
> >
> > Best wishes,
> >
> > Alan
> >
>


Re: Please recommend NuttX

2024-07-11 Thread michal . lyszczek
On 2024-07-11 06:19:55, Alan C. Assis wrote:
> I wasn't expecting anything different from ARM:
> 
> https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644/3
> 
> This is why I think RISC-V will win!

That's right Alan, you tell them!

And yeah, I agree with you. It would take him less time to edit his post
than to reply to you.

-- 
.-.---.--.-.
| Michal Lyszczek | Embedded C, Linux |   Company Address|  .-. opensource |
| +48 727 564 419 | Software Engineer | Akacjowa 10a; 55-330 |  oo|  supporter |
| https://bofc.pl `.--: Brzezinka Sredzka PL | /`'\  & |
| GPG FF1EBFE7E3A974B1 | Bits of Code | NIP:   813 349 58 78 |(\_;/) programer |
`--^--^--^-'


signature.asc
Description: PGP signature


Re: Please recommend NuttX

2024-07-11 Thread Alan C. Assis
Good idea! Thank you Gábor!

On Thu, Jul 11, 2024 at 6:30 AM Gábor Kiss-Vámosi 
wrote:

> At least you can add a link to NuttX in your comment.
>
> Gabor
>
> Alan C. Assis  ezt írta (időpont: 2024. júl. 11., Cs,
> 11:20):
>
> > I wasn't expecting anything different from ARM:
> >
> > https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644/3
> >
> > This is why I think RISC-V will win!
> >
> > BR,
> >
> > Alan
> >
> > On Wed, Jul 10, 2024 at 6:34 PM Alan C. Assis  wrote:
> >
> > > Dear NuttXers,
> > >
> > > Just as you were talking about NuttX awareness, see that:
> > >
> > > https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644
> > >
> > > They recommended FreeRTOS and Zephyr (no surprise here), but no
> reference
> > > to NuttX.
> > >
> > > Please help us to get awareness about NuttX.
> > >
> > > If you don't want to write a post, just click Like on my post, it will
> be
> > > enough.
> > >
> > > Best wishes,
> > >
> > > Alan
> > >
> >
>


Re: Please recommend NuttX

2024-07-11 Thread Alan C. Assis
Thank you Michal,

I just updated my comment and I reminded him that everytime we ask for help
from RISCV they help us.

BR,

Alan

On Thu, Jul 11, 2024 at 6:30 AM  wrote:

> On 2024-07-11 06:19:55, Alan C. Assis wrote:
> > I wasn't expecting anything different from ARM:
> >
> > https://forums.mbed.com/t/important-update-on-mbed-end-of-life/23644/3
> >
> > This is why I think RISC-V will win!
>
> That's right Alan, you tell them!
>
> And yeah, I agree with you. It would take him less time to edit his post
> than to reply to you.
>
> --
>
> .-.---.--.-.
> | Michal Lyszczek | Embedded C, Linux |   Company Address|  .-.
> opensource |
> | +48 727 564 419 | Software Engineer | Akacjowa 10a; 55-330 |  oo|
> supporter |
> | https://bofc.pl `.--: Brzezinka Sredzka PL | /`'\
> & |
> | GPG FF1EBFE7E3A974B1 | Bits of Code | NIP:   813 349 58 78 |(\_;/)
> programer |
>
> `--^--^--^-'
>


Using const in function arguments.

2024-07-11 Thread Saurav Pal
Hi all,

Suppose I have a pointer that I want to pass through function parameters.
In the function, neither is the pointer reassigned, nor is the thing it
points to modified in any form.

So, I would assume its function argument signature to be like FAR const
struct my_struct * const ptr (The second "const" is my focus here).
Similarly for things like const uint8_t my_num, etc. as well.

However, I have not really seen much use of specifying constants using
const (in the way I have mentioned above). Most of the examples I see are
of FAR const struct my_struct * ptr. I have heard the compiler can make
better optimizations for const, and because of this, I try to spam const
anywhere and everywhere I can. But I don't see too many such usages across
the codebase, so I was wondering why that is (or I just maybe reading the
code wrong, in which case, forgive me 🙏).

Regards,
Saurav Pal.


Using external libraries with NuttX

2024-07-11 Thread Michal Lenc
Hello all,

I am currently facing the problem of using external library with NuttX.
The support is already prepared in mainline in directory external/ which
is compiled if Kconfig and Makefile are present in the directory. This
is all fine as I symlink my library to external/ directory so I get to
compile the source code and have all the configuration I need. The
directory looks somewhat like:

external

    my_project

        Make.defs and Kconfig

    Kconfig and Makefile

The problem is with the headers. If I use the same approach as in
drivers/ or so libraries and add my headers to CFLAG, they are not
accessible from an application. The only thing that works so far is
adding the CFLAGs in top level Make.defs linked from the board
directory; then the headers are exported and everything works fine.

Is this the only possible solution so far or is there some other
flag/approach how to do it more nicely? The ideal approach from my point
of view would be not to edit top level Make.defs at all. Am I missing
some additional flag? Thanks.

Michal