I think that we should consider making the last release from a series an
LTS release and patch that one for a decided period (ex 12 months)
This way a downstream project that uses an older release can always use the
latest release that is API compatible without the need to patch the project.
If yo
On Fri, Sep 18, 2020 at 3:16 PM Flavio Castro Alves Filho
wrote:
>
> Hello Matias,
>
> Em sex., 18 de set. de 2020 às 16:26, Matias N. escreveu:
> >
> > Hi Flavio,
> > please have a look at our new documentation, which you may find helpful:
> >
> > https://nuttx.apache.org/docs/latest/
> >
>
> I
On Fri, Sep 18, 2020 at 3:17 PM Flavio Castro Alves Filho
wrote:
> I am studying NuttX for a new project. I am using Nucleo-F429ZI as
> reference, which is quite a complete board and has a large memory for
> testing.
>
> I followed some instructions from the internet (mostly from NuttX
> website)
Ok! Do report your issues, we're trying to improve the on boarding experience.
Best,
Matias
On Fri, Sep 18, 2020, at 19:15, Flavio Castro Alves Filho wrote:
> Hello Matias,
>
> Em sex., 18 de set. de 2020 às 16:26, Matias N. escreveu:
> >
> > Hi Flavio,
> > please have a look at our new documen
Hello Matias,
Em sex., 18 de set. de 2020 às 16:26, Matias N. escreveu:
>
> Hi Flavio,
> please have a look at our new documentation, which you may find helpful:
>
> https://nuttx.apache.org/docs/latest/
>
I did ... that's how I found most of the problems to have this initial
version running.
>
Hi Flavio,
please have a look at our new documentation, which you may find helpful:
https://nuttx.apache.org/docs/latest/
Most boards have a "nsh" documentation which should be a good start (this
is also explained in the documentation).
I don't know the particular status of this board, but usual
Hello,
I am studying NuttX for a new project. I am using Nucleo-F429ZI as
reference, which is quite a complete board and has a large memory for
testing.
I followed some instructions from the internet (mostly from NuttX
website) and I could compile and run a binary on the board. Including
executin
I completely understand that it takes work to patch and regression test
previous releases, but I just want to understand our policy and threshold
for what gets backported.
There should be an established policy. I agree on that.
In the old BDFL model, I only updated releases via patches and
Hello Team,
We are trying to include Renesas RX65N architecture in GitHub pre-check which
requires code to have 0 warnings to be successful.
Call to up_copystate() in the below functions produces warnings in NuttX common
files:
arch/renesas/src/common/up_blocktask.c: up_block_task()
arch/renesa
I've debugged this issue and found out that in such moments fs_buffer is
not filled fully - if I read the same cluster from pc - fat chain is ok.
Moreover I found that after a few steps in debug fs_buffer gets fully
filled as it is on an sd card. So it looks like the issue is related to
hardware r
10 matches
Mail list logo
