It's going to be a clear trademark problem and the GitHub organization is
controlled by random people. Most PPMC members have no control over it.
On Sat, Oct 16, 2021, 11:51 PM Alin Jerpelea wrote:
> I propose that we delete the contents of https://github.com/NuttX/ and we
> host there only the
I propose that we delete the contents of https://github.com/NuttX/ and we
host there only the components that have conflicting licenses under
https://github.com/NuttX/nuttx-extras
On Sun, Oct 17, 2021, 06:45 Xiang Xiao wrote:
> Some tools(e.g. kconfig-frontend) are critical for NuttX, but in a
Some tools(e.g. kconfig-frontend) are critical for NuttX, but in an
unmaintained state, so we have to maintain our own version.
Two options here:
1. Host on https://bitbucket.org/nuttx/, Greg needs to share the admin
right to all PPMC/Commmiter member.
2. Host on https://github.com/NuttX
I have performed the testing. I sent segments with size of 32 bytes in
a loop. NuttX source code is based on SHA-1 =
1e2560267898f413c93c5fb616ddc5b1d4d07184.
As a TCP host I used Linux kernel 4.19.
In case of forcing TCP_QUICKACK option to 1 in Linux I added the
following line after recv():
re
> So my question is: If Nuttx requires C11 features, presumably the
> Microchip Studio GCC is based on a later version than 4.4, and if so,
> where's the source
NuttX common code does not depend on C11. In fact the coding standard
requires that all shared code conform to C89. Being able to wo
Those are pretty old. These are old too:
http://ww1.microchip.com/downloads/archive/avr32-gnu-toolchain-3.4.0.332-source.zip
There are even old sources here:
https://www.microchip.com/en-us/development-tools-tools-and-software/avr-and-sam-downloads-archive
There slightly newer gcc-avr32 RPMs ava
I found this:
https://github.com/embecosm/avr32-gcc
https://github.com/embecosm/avr32-binutils-gdb
https://github.com/embecosm/avr32-newlib
Hope this helps.
Augusto.
> From: Martin Guy
> Date: Sat, 16 Oct 2021 13:41:40 +0200
> Subject: What's the AVR32 GCC in Microchip Studio and where's its s
There isn't really a big difference between IDF's toolchain and the one
from Sifive, this is why we didn't add both.
Are you having issues running the one from SiFive?
The CROSSDEV variable will just have the name of the toolchain. If we want
to add another toolchain we add another ifeq in
riscv/r
On Sat, Oct 16, 2021 at 6:37 PM Tomasz CEDRO wrote:
>
> On Sat, Oct 16, 2021 at 6:23 PM Tomasz CEDRO wrote:
> >
> > I have managed to build and install Debian version of
> > kconfig-frontends. Local testing for now.
> >
> > The problem I have encountered now is the `tools/configure.sh` uses
> > `ma
On Sat, Oct 16, 2021 at 6:15 PM Tomasz CEDRO wrote:
>
> On Sat, Oct 16, 2021 at 6:11 PM Abdelatif Guettouche
> wrote:
> >
> > > I could not find detailed information on how to setup RISC-V toolchain
> > except just using "generic toolchain":
> > https://nuttx.apache.org/docs/latest/platforms/risc-
Agreed it will just complicate things moving towards graduation. I had
asked for it to be taken down a long time ago.
--Brennan
On Sat, Oct 16, 2021, 7:10 AM Gregory Nutt wrote:
> No, https://github.com/NuttX/nuttx is just garbage and should be deleted.
> It has nothing to do with Apache NuttX
After fixing the kconfig and tools/configure problem now we need to
fix the compiler / toolchain detection issue on esp32-c3 risc-v.
(venv38zephyr) ./tools/configure.sh esp32c3-devkit:ble
No configuration change.
(venv38zephyr) gmake
Create .version
Create version.h
gmake[1]: Entering directory '
On Sat, Oct 16, 2021 at 6:23 PM Tomasz CEDRO wrote:
>
> I have managed to build and install Debian version of
> kconfig-frontends. Local testing for now.
>
> The problem I have encountered now is the `tools/configure.sh` uses
> `make` for builds. On BSD systems BSD version of `make` is used by
> de
I have managed to build and install Debian version of
kconfig-frontends. Local testing for now.
The problem I have encountered now is the `tools/configure.sh` uses
`make` for builds. On BSD systems BSD version of `make` is used by
default. GNU make is named `gmake` here.
Will try to patch that ou
I have managed to build and install Debian version of
kconfig-frontends on FreeBSD.
Will try that one out and report back in dedicated threads :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Sat, Oct 16, 2021 at 6:11 PM Abdelatif Guettouche
wrote:
>
> > I could not find detailed information on how to setup RISC-V toolchain
> except just using "generic toolchain":
> https://nuttx.apache.org/docs/latest/platforms/risc-v/esp32c3/index.html
>
> There is a link there to download the too
> I could not find detailed information on how to setup RISC-V toolchain
except just using "generic toolchain":
https://nuttx.apache.org/docs/latest/platforms/risc-v/esp32c3/index.html
There is a link there to download the toolchain used, here:
https://static.dev.sifive.com/dev-tools/riscv64-unkno
Removing is one time destructive operation. Something may be still
necessary from there.
Archiving with a redirect message seems safer solution, it will be
still available to read/download but no updates, then things could be
removed after careful examination if/when necessary :-)
Tomek
On Sat,
Allright, except for the FreeBSD works, I would like to have a working
reference point based on Linux Debian 10.10, so I have created a VM.
I could not find detailed information on how to setup RISC-V toolchain
except just using "generic toolchain":
https://nuttx.apache.org/docs/latest/platforms/
I don't know what to do with the submodule repositories: Documentation,
configs, and arch. Should these be retained online somewhere so that those
very old releases could be built?
Those directories were originally part of nuttx/, then moved to submodules,
then later merged back under nuttx/. T
BTW the version of the OS we have there, is _very_ old. The description says:
> This is an old snapshot of NuttX from when arch/, configs/, and
> Documentation/ were submodules
On Sat, Oct 16, 2021 at 5:43 PM Abdelatif Guettouche
wrote:
>
> I can access it and deleting it is a click away (prov
I can access it and deleting it is a click away (provided that Github
doesn't ask for every members approval)
On Sat, Oct 16, 2021 at 5:17 PM Gregory Nutt wrote:
>
> I just tried accessing github.com/nuttx and it appears that I can no longer
> see project information. I don't know what is going
I just tried accessing github.com/nuttx and it appears that I can no longer
see project information. I don't know what is going on with those
repositories.
On Sat, Oct 16, 2021 at 9:09 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> People who have admin access to that org are
People who have admin access to that org are all committers/PPMC members.
If we want to take it down we can do that.
As Greg mentioned earlier, that was supposed to host GPL repos and the os
and apps version there are outdated.
On Sat, Oct 16, 2021, 16:53 Tomasz CEDRO wrote:
> I have contacted G
I have contacted GitHub support in that matter. Maybe taking ownership
of that org / repo will be possible.
Tomek
On Sat, Oct 16, 2021 at 4:39 PM Gregory Nutt wrote:
>
> The project never was at that location, https://github.com/NuttX.
> Everything there is of uncertain lineage and uncertain and
The project never was at that location, https://github.com/NuttX.
Everything there is of uncertain lineage and uncertain and should just be
removed or converted to mirrors.
Prior to moving to https://github.com/apache/incubator-nuttx*, the project
was on bitbucket at https://bitbucket.org/nuttx/.
On Fri, Oct 15, 2021 at 10:44 PM Tomasz CEDRO wrote:
>
> Returning to KCONFIG :-)
>
> I have talked to Debian kconfig-frontends maintainer Philippe Thierry:
>
> https://packages.debian.org/stable/kconfig-frontends
>
> He confirmed that kconfig-frontends is abandoned. They use own git
> repository w
Maybe you could re-gain access Gregory manage users and put it in an
"archived state" with a note that the project moved to Apache
organization? :-)
That way nothing will be deleted, while note on new upstream will
redirect users to a new place decreasing confusion.
There is a chance that someone
No, https://github.com/NuttX/nuttx is just garbage and should be deleted.
It has nothing to do with Apache NuttX and I don't think anything has been
touched there in months.
A thought was that this could be a place to keep GPL tools and applications
that are needed with NuttX but that are incompat
Hi Martin,
On 10/16/21, Martin Guy wrote:
> Hi!
>My company wishes to port NuttX to its AVR32 board, and I see on
> https://nuttx.apache.org/docs/latest/introduction/detailed_support.html#microchip-avr32
> "This port requires a special GNU avr32 toolchain available from
> atmel.com website. T
Hello world :-)
Another thing I found confusing a bit for a newcomer is the dual
repository model:
1. https://github.com/NuttX/nuttx
2. https://github.com/apache/incubator-nuttx
There is not information or redirect on 1 that development takes place on 2.
Is 2 going to become 1 back again when in
Hello Yann,
You are marked as the author of the kconfig-frontends in a release
package AUTHORS file. This package is a core dependency of the NuttX
RTOS. It seems that development of the package has been abandoned..?
Can you please confirm if the maintenance of the package has been
abandoned? If
Hi!
My company wishes to port NuttX to its AVR32 board, and I see on
https://nuttx.apache.org/docs/latest/introduction/detailed_support.html#microchip-avr32
"This port requires a special GNU avr32 toolchain available from
atmel.com website. This is a windows native toolchain and so can be
used o
Hello,
Who could point out a way to implement a Hall sensor driver for say the
Hamlin 55100? Is there an example (driver) which is already in the
repository?
Say an "attachInterrupt" routine like in the Arduino stack?
Thanks again.
Ben
34 matches
Mail list logo
