>
> Thank you for sharing this CH32V30x porting repository.
>
For anyone following along, this was an accident. The "real" repo (to which
I'm about to commit more stuff) is at
https://github.com/robertlipe/incubator-nuttx
> I think the right way to handle the GPIO is like STM32 and other
> arche
>
>
> >
> > In sum, it's not that NuttX is hard. It's that *NuttX IS MADE HARD,
> > PROBABLY ON PURPOSE*
>
I told myself to let NuttX go silently (I did unsub), but this overall
story matches several I've seen.
The core architecture is just weird in ways that don't encourage fresh
blood. Whitespa
of our control. It's pretty
> new too, so we too have to get used to it. As Nathan said, this only
> applies to first time contributors. Subsequent contributions should go a
> bit smoother.
>
> On Wed, Jun 23, 2021, 3:37 PM Nathan Hartman
> wrote:
>
> > On Tue,
>
>
> > The presubmit flips out about C99 comments. Even that's too radical. So
> > much for being king. :-)
>
> You can use C99, but you cannot forgot to follow the Coding Style, //
> comments shouldn't be used :-)
>
It's actually worse than that. You can use C99 comments at the end of a line
but
On Mon, Jun 14, 2021 at 1:02 PM Alan Carvalho de Assis
wrote:
> Normally only common code on NuttX needs to follow the C89 standard
>
The presubmit flips out about C99 comments. Even that's too radical. So
much for being king. :-)
> Also should use tools/checkpatch.sh to check your patch/files
Hi.
I've been part of open source since the 80's, including at the development
tools and OS levels, but I'm new to Nuttx. My hobby of late has centered
around the RISC-V SoCs and I see that Nuttx has good coverage on the large
microcontroller class devices like BL602 and K210 and is just now getti
