Hi Andrew,

This is a nice idea!

So, currently these two are the most critical issues, right?

Best Regards,

Alan

On Thu, Apr 11, 2024 at 8:44 PM Andrew Dennison <
andrew.denni...@motec.com.au> wrote:

> Hi Alan,
>
> We have reported the main problems we have observed in the example issues
> mentioned below (#9840 and #11189) and also have some open PR for
> performance related features. Our desire is to focus our team on product
> functionality so we would like to offer to fund someone to help with any
> Nuttx challenges we have so we can get them resolved without relying on
> community members to generously donate their time.
>
> In #9840, for example, we provided an example that demonstrates something
> we observed but also suspect that the Linux Test Project _may_ also be
> useful to confirm if this is a Nuttx problem.
>
> As you mentioned, having something in ostest to detect the issue and verify
> the fix / catch regressions would be ideal.
>
> Kind regards,
>
> Andrew Dennison
> Chief Architect and Hardware Team Lead
>
> On Thu, 11 Apr 2024 at 04:18, Alan C. Assis <acas...@gmail.com> wrote:
>
> > Hi Andrew,
> >
> > Could you please open a public issue to report these issues (case you
> > haven't yet).
> >
> > Also if you have some testing examples to trigger these issues, we could
> > include it into our ostest to avoid it happening again.
> >
> > BR,
> >
> > Alan
> >
> > On Tue, Apr 9, 2024 at 3:45 AM Andrew Dennison <
> > andrew.denni...@motec.com.au>
> > wrote:
> >
> > > Hi Nuttx community,
> > >
> > > We are actively working with nuttx and RISCV (RV32) and have
> contributed
> > > several PR to improve support for kernel mode with litex:
> > >
> > >
> >
> https://nuttx.apache.org/docs/latest/platforms/risc-v/litex/cores/vexriscv_smp/index.html
> > > .
> > >
> > > Along the way we have identified several issues and would like to offer
> > to
> > > pay for someone with appropriate experience to investigate and upstream
> > any
> > > fixes identified. Some examples:
> > >
> > > Experiencing possible race condition with pthread_cond_timedwait. #9840
> > > <https://github.com/apache/nuttx/issues/9840>
> > > Unexpected behaviour with poll and tickless scheduler #11189
> > > <https://github.com/apache/nuttx/issues/11189>
> > >
> > > Please contact us directly if you feel you could help with either of
> > these
> > > issues or potentially some of the other recent issues here:
> > > https://github.com/apache/nuttx/issues?q=is%3Aopen+author%3Ag2gps+
> > >
> > > Kind regards,
> > >
> > > Andrew Dennison
> >
>
> >
>
> --
> *MoTeC Pty Ltd*
>
> 121 Merrindale Drive
> Croydon South 3136
> Victoria Australia
> *T: *61 3 9761 5050
> *W: *www.motec.com.au <https://www.motec.com.au/>
>
>
> --
>  <http://www.facebook.com/motec.global>
> <http://www.youtube.com/user/MoTeCAustralia>
> <https://www.instagram.com/motec_global/>
> <https://www.linkedin.com/company/motec-global>
>
>
> --
>  <https://www.motec.com.au>
>
> --
>
>
> Disclaimer Notice: This message, including any attachments, contains
> confidential information intended for a specific individual and purpose
> and
> is protected by law. If you are not the intended recipient you should
> delete this message. Any disclosure, copying, or distribution of this
> message or the taking of any action based on it is strictly prohibited.
>

Reply via email to