Re: Introduction + incoming RISC-V port(s)

> > > > > > 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

Re: Introduction + incoming RISC-V port(s)

Hi Grr, I agree with many points you raised: the amount of options inside NuttX menuconfig is really a bad thing, it is like a maze. You need to track many configs until you get everything in place and get things done. But in the other hand it is what let you to fine tune the system for your need.

Re: Introduction + incoming RISC-V port(s)

El mar, 3 ago 2021 a las 6:49, Alan Carvalho de Assis () escribió: > Unfortunately NuttX is not for faint of heart people (same to the > Linux kernel) I don't know about Linux but what makes NuttX not for the faint of heart is you, the core programmers. I explain why: *Config Nightmare* NuttX me

Re: Introduction + incoming RISC-V port(s)

Hi Robert, We all here appreciate your effort to make it happen, but I think you also started things very badly. No matter what was your previous culture, we never arrive at someone home and start talking bad things about their furniture and/or their children. We all here was very patience to you

Re: Introduction + incoming RISC-V port(s)

This iteration of BeagleV hardware is canceled . Given the friction of landing PR#3965, I'm just going to abandon it and mark that CL closed and will be unsubscribing from the lists. There's probably nothing worth heroic efforts to preserve; only a few of those 108 commits we

Re: Introduction + incoming RISC-V port(s)

*So I've kicked that back in, but it appears I have to wait for a (gasp)human**to push a button*. This is actually a Github thing and is outside 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 contri

Re: Introduction + incoming RISC-V port(s)

On Tue, Jun 22, 2021 at 11:12 PM Robert Lipe wrote: > > > > > > > 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 ac

Re: Introduction + incoming RISC-V port(s)

> > > > 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

Re: Introduction + incoming RISC-V port(s)

s/forgot/forget/ On 6/22/21, Alan Carvalho de Assis wrote: > Hi Robert, > > On 6/22/21, Robert Lipe wrote: >> 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 C9

Re: Introduction + incoming RISC-V port(s)

Hi Robert, On 6/22/21, Robert Lipe wrote: > 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. :-) > You ca

Re: Introduction + incoming RISC-V port(s)

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

Re: Introduction + incoming RISC-V port(s)

> > There's a LOT of duplication within arch/risc-v and where there is > divergence, it's not always clear it's intentional or if it's just missed > merges. It's an area where weak symbols (don't call a function if it wasn't > linked) and C++ virtual overrides could really clean things up. I g

Re: Introduction + incoming RISC-V port(s)

Hi Robert, This is an amazing news! Thank you for doing it and for willing to include it on NuttX mainling. Normally only common code on NuttX needs to follow the C89 standard because some microcontrollers don't have newer compiler. So, that said, inside arch/ and boards/ you are king, you can u