Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
68k cross-development on FreeBSD (or any other unixlike platform) is pretty straightforward. Crosstool-NG trivialises generating the toolchain, and the current state of 68k support in the FSF tools is quite good. LLVM is getting there, but I feel like the backend needs more work. Unless the NuttX cross-compilation tooling has changed drastically, I wouldn't expect you'll need to do anything substantially different from any other GCC-based target. Thinking a bit more about the issue I got stuck on, I suspect it may have been related to not having a standardised way to generate a deferred interrupt akin to PendSV. I was doing a lot of ARMv7M work at the time, and I was probably trying to exploit the otherwise fairly similar nature of the two architectures. Good luck! = Mike > On Oct 13, 2022, at 9:02 AM, Tomek CEDRO wrote: > > Hello Alan and Mike :-) > > Most of us cyberpunks have this problem with time division between > what we want to do and what we have to do :-) > > Mike, your core work might be a good fundament for other people, when > it is in the upstream someone can pick a task in a free moment, and > piece by piece it may lead to a working solution.. this will be also a > fun / hobby project for me :-) > > I am also in contact with Hans from BeastieLabs, he did crosscompile > Minix to Atari ST on FreeBSD some time ago. Although there is no port, > only a build script, this also may be a good starting point for > MC68000 crossdevelopment on FreeBSD :-) > > http://www.beastielabs.net/minix.html > http://www.beastielabs.net/crossdev.html > > Best regards :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Thank You Mike! Have a good weekend :-) Tomek On Fri, Oct 14, 2022 at 9:19 PM Mike Smith wrote: > > 68k cross-development on FreeBSD (or any other unixlike platform) is pretty > straightforward. Crosstool-NG trivialises generating the toolchain, and the > current state of 68k support in the FSF tools is quite good. LLVM is getting > there, but I feel like the backend needs more work. > > Unless the NuttX cross-compilation tooling has changed drastically, I > wouldn't expect you'll need to do anything substantially different from any > other GCC-based target. > > Thinking a bit more about the issue I got stuck on, I suspect it may have > been related to not having a standardised way to generate a deferred > interrupt akin to PendSV. I was doing a lot of ARMv7M work at the time, and I > was probably trying to exploit the otherwise fairly similar nature of the two > architectures. > > Good luck! > > = Mike > > > On Oct 13, 2022, at 9:02 AM, Tomek CEDRO wrote: > > > > Hello Alan and Mike :-) > > > > Most of us cyberpunks have this problem with time division between > > what we want to do and what we have to do :-) > > > > Mike, your core work might be a good fundament for other people, when > > it is in the upstream someone can pick a task in a free moment, and > > piece by piece it may lead to a working solution.. this will be also a > > fun / hobby project for me :-) > > > > I am also in contact with Hans from BeastieLabs, he did crosscompile > > Minix to Atari ST on FreeBSD some time ago. Although there is no port, > > only a build script, this also may be a good starting point for > > MC68000 crossdevelopment on FreeBSD :-) > > > > http://www.beastielabs.net/minix.html > > http://www.beastielabs.net/crossdev.html > > > > Best regards :-) > > Tomek > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hello Alan and Mike :-) Most of us cyberpunks have this problem with time division between what we want to do and what we have to do :-) Mike, your core work might be a good fundament for other people, when it is in the upstream someone can pick a task in a free moment, and piece by piece it may lead to a working solution.. this will be also a fun / hobby project for me :-) I am also in contact with Hans from BeastieLabs, he did crosscompile Minix to Atari ST on FreeBSD some time ago. Although there is no port, only a build script, this also may be a good starting point for MC68000 crossdevelopment on FreeBSD :-) http://www.beastielabs.net/minix.html http://www.beastielabs.net/crossdev.html Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hi Mike, Thank you very much for your fast reply. I'm CC our mailing list (I hope you don't get angry with me) because your words are really inspiring for everyone here! Case you find your initial M68K port please let us know! I think it should be a nice achievement for NuttX to retro-computing community. We are missing you! You was always prone to help everyone and your level of knowledge is remarkable, I learned a lot from you! BR, Alan On 10/12/22, Mike Smith wrote: > G'day Alan, > > I worked on a port to the 68k a while back, but it stalled for various > reasons; real work got in the way, and I recall at least one technical issue > related to interrupt / exception handling (likely surmountable, but I don't > remember the details). > > As you see, I'm still contactable 8) but as Greg notes I had to put my > involvement with NuttX (and many other things) on hold in order to focus on > paying work. Regrettable. 8( > > I did a little digging around, but I haven't been able to locate the working > copy. If I do I'll pass it along, but it wasn't anything revolutionary and > could probably be replicated in a couple of days - especially with the > emulation options now available. > > As an aside, the current state of NuttX is simply remarkable. I haven't had > time to look at the community, but the continued growth and maturity of the > code is an inspiration, and I have used it as an example to other teams more > than once. Whatever the community is doing, it certainly looks like it > works. 8) > > Regards, > > = Mike > >> On Oct 10, 2022, at 4:24 PM, Alan C. Assis wrote: >> >> Hi Mike, >> >> How are you? >> >> Greg commented about you today, he said you did the NuttX port to Motorola >> 68k ! >> >> Is that true? If so, could you share it and we'll clean-up and upstream >> it. >> >> BR, >> >> Alan >> >> -- Forwarded message -- >> From: Gregory Nutt >> Date: Mon, 10 Oct 2022 16:49:26 -0600 >> Subject: Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2] >> To: dev@nuttx.apache.org >> >> Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if >> he >> completed it or not, but the port never came upstream. Mike is no longer >> involved with NuttX and probably not contactable. If anyone out there in >> PX4 land knows where Mike kept his code, that might be helpful. >> >> >> >> A port to one of the WDC 65xx parts would also be interesting: >> https://www.westerndesigncenter.com/ >> >> >> >> On Mon, Oct 10, 2022 at 4:12 PM Sebastien Lorquet >> wrote: >> >>> Hi, >>> >>> If you want to play with 68k, tell me, the ti68k calculators >>> (ti89,92+,v200,titanium) should be great platforms: 256K RAM and 2-4M >>> flash, full keyboard and lcd screen. >>> >>> They have some peculiarities, I could help with drivers or find friends >>> that could. >>> >>> The cemetech/tiplanet communities should like it. >>> >>> Sebastien >>> >>> On 10/8/22 18:06, Tomek CEDRO wrote: >>>> On Sat, Oct 8, 2022 at 4:58 PM Alan C. Assis wrote: >>>>> Hi Tomek, >>>>> I think 6502 compiler are evolving, but I don't know if they are >>> compatible. >>>>> There is a interesting comparison here: >>>>> https://gglabs.us/node/2293 >>>>> CC. Gabriele here, since I don't know if here is in our list! >>>> Thank you Alan :-) 8-bit platforms are on list, but before I would >>>> like to make smooth out-of-the box experience with NuttX on FreeBSD, >>>> then port MicroPython to NuttX, then as a training in porting I would >>>> prefer to target 16-bit MC68000 in the first place (Atari + Amiga), >>>> then 8-bit Atari, in that order, and all of that in my free time >>>> between other tasks, so there is no rush :-) >>>> >>> > >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On 10/11/2022 3:14 AM, Tomek CEDRO wrote: On Tue, Oct 11, 2022 at 12:49 AM Gregory Nutt wrote: Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if he completed it or not, but the port never came upstream. Mike is no longer involved with NuttX and probably not contactable. If anyone out there in PX4 land knows where Mike kept his code, that might be helpful. Hello Gregory :-) As I have two MC68000 machines right now (Atari ST Mega1 and Amiga 600) this seems to be simpler task as the first step in porting.. at least we have standard serial port in those machines and much more memory to operate on :-) A port to one of the WDC 65xx parts would also be interesting: https://www.westerndesigncenter.com/ Sure thing! 8-bit machines are smaller and porting may be considerably harder so this seems good second step after training on 16-bit machines :-) Many of the WDC 65xx chips support 16 processing on a 16MB address space: https://www.westerndesigncenter.com/wdc/chips.php These are newer designs, but developed by the original 6800/6502 patent holder: https://www.westerndesigncenter.com/wdc/WDC_Founder.php
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On Tue, Oct 11, 2022 at 12:49 AM Gregory Nutt wrote: > Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if he > completed it or not, but the port never came upstream. Mike is no longer > involved with NuttX and probably not contactable. If anyone out there in > PX4 land knows where Mike kept his code, that might be helpful. Hello Gregory :-) As I have two MC68000 machines right now (Atari ST Mega1 and Amiga 600) this seems to be simpler task as the first step in porting.. at least we have standard serial port in those machines and much more memory to operate on :-) > A port to one of the WDC 65xx parts would also be interesting: > https://www.westerndesigncenter.com/ Sure thing! 8-bit machines are smaller and porting may be considerably harder so this seems good second step after training on 16-bit machines :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Several years ago Mike Smith did a 68000 port of NuttX. I’m not sure if he completed it or not, but the port never came upstream. Mike is no longer involved with NuttX and probably not contactable. If anyone out there in PX4 land knows where Mike kept his code, that might be helpful. A port to one of the WDC 65xx parts would also be interesting: https://www.westerndesigncenter.com/ On Mon, Oct 10, 2022 at 4:12 PM Sebastien Lorquet wrote: > Hi, > > If you want to play with 68k, tell me, the ti68k calculators > (ti89,92+,v200,titanium) should be great platforms: 256K RAM and 2-4M > flash, full keyboard and lcd screen. > > They have some peculiarities, I could help with drivers or find friends > that could. > > The cemetech/tiplanet communities should like it. > > Sebastien > > On 10/8/22 18:06, Tomek CEDRO wrote: > > On Sat, Oct 8, 2022 at 4:58 PM Alan C. Assis wrote: > >> Hi Tomek, > >> I think 6502 compiler are evolving, but I don't know if they are > compatible. > >> There is a interesting comparison here: > >> https://gglabs.us/node/2293 > >> CC. Gabriele here, since I don't know if here is in our list! > > Thank you Alan :-) 8-bit platforms are on list, but before I would > > like to make smooth out-of-the box experience with NuttX on FreeBSD, > > then port MicroPython to NuttX, then as a training in porting I would > > prefer to target 16-bit MC68000 in the first place (Atari + Amiga), > > then 8-bit Atari, in that order, and all of that in my free time > > between other tasks, so there is no rush :-) > > >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hi, If you want to play with 68k, tell me, the ti68k calculators (ti89,92+,v200,titanium) should be great platforms: 256K RAM and 2-4M flash, full keyboard and lcd screen. They have some peculiarities, I could help with drivers or find friends that could. The cemetech/tiplanet communities should like it. Sebastien On 10/8/22 18:06, Tomek CEDRO wrote: On Sat, Oct 8, 2022 at 4:58 PM Alan C. Assis wrote: Hi Tomek, I think 6502 compiler are evolving, but I don't know if they are compatible. There is a interesting comparison here: https://gglabs.us/node/2293 CC. Gabriele here, since I don't know if here is in our list! Thank you Alan :-) 8-bit platforms are on list, but before I would like to make smooth out-of-the box experience with NuttX on FreeBSD, then port MicroPython to NuttX, then as a training in porting I would prefer to target 16-bit MC68000 in the first place (Atari + Amiga), then 8-bit Atari, in that order, and all of that in my free time between other tasks, so there is no rush :-)
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On Sat, Oct 8, 2022 at 4:58 PM Alan C. Assis wrote: > > Hi Tomek, > I think 6502 compiler are evolving, but I don't know if they are compatible. > There is a interesting comparison here: > https://gglabs.us/node/2293 > CC. Gabriele here, since I don't know if here is in our list! Thank you Alan :-) 8-bit platforms are on list, but before I would like to make smooth out-of-the box experience with NuttX on FreeBSD, then port MicroPython to NuttX, then as a training in porting I would prefer to target 16-bit MC68000 in the first place (Atari + Amiga), then 8-bit Atari, in that order, and all of that in my free time between other tasks, so there is no rush :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Fixed email! On 10/8/22, Alan C. Assis wrote: > Hi Tomek, > > I think 6502 compiler are evolving, but I don't know if they are > compatible. > > There is a interesting comparison here: > > https://gglabs.us/node/2293 > > CC. Gabriele here, since I don't know if here is in our list! > > BR, > > Alan > > On 10/8/22, Tomek CEDRO wrote: >> By the way, I also found some tools for MOS6502 in the ports tree :-) >> >> # make quicksearch key="6502" >> Port: acme-0.97.r319,1 >> Path: /usr/ports/devel/acme >> Info: Crossassembler for 6502, 65c02 and 65816 processors >> >> Port: cc65-2.19 >> Path: /usr/ports/devel/cc65 >> Info: Cross-compiler for 6502-based systems >> >> Port: dxa65-0.1.4 >> Path: /usr/ports/devel/dxa65 >> Info: Disassembler for MOS 6502 and compatible CPUs >> >> Port: vasm-1.8c >> Path: /usr/ports/devel/vasm >> Info: Portable 6502 6800 arm c16x jagrisc m68k ppc vidcore x86 z80 >> assembler >> >> Port: xa65-2.3.11 >> Path: /usr/ports/devel/xa65 >> Info: Two-pass cross-assembler for MOS 6502 and compatible CPUs >> >> Port: p5-Acme-6502-0.77_2 >> Path: /usr/ports/emulators/p5-Acme-6502 >> Info: Pure Perl 65C02 simulator >> >> Port: nesasm-20040314_1 >> Path: /usr/ports/lang/nesasm >> Info: 6502 assembler with specific NES support >> >> >> Not sure about dedicated toolchain for MC68000 (16-bit Atari and >> Amiga) if there needs to be one or generic compiler can cross compile >> that target.. but I will know that in some time as I have both Amiga >> 600 and Atari ST Mega1 :-) >> >> Best regards :-) >> Tomek >> >> >> On Sat, Oct 8, 2022 at 3:15 PM Tomek CEDRO wrote: >>> >>> Well, toolchain is another thing on the BSD TODO list :-) You either >>> need to have Espressif toolchain installed and in path or you can >>> provide your own or system toolchain by hand durign build. >>> >>> I am on a trip right now with my backup laptop that is not my main >>> development workstation, sorry, but the summary is below. >>> >>> 1. Because FreeBSD can natively emulate Linux ELF binaries, I did a >>> trick with support of Espressif that allows download and install Linux >>> tools on FreeBSD with ESP-IDF. That works fine.. but it would be >>> perfect to build and distribute also toolchain binaries for FreeBSD by >>> Espressif. So far I have used ESP IDF Linux tools on FreeBSD for >>> initial experiments on ESP32 and ESP32-C3. >>> >>> % uname -a >>> FreeBSD 0xCFMX4 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64 >>> >>> % ls -1 ~/.espressif/tools >>> esp32s2ulp-elf >>> esp32ulp-elf >>> openocd-esp32 >>> riscv32-esp-elf >>> xtensa-esp32-elf >>> xtensa-esp32s2-elf >>> xtensa-esp32s3-elf >>> >>> That gives: >>> >>> % ./xtensa-esp32-elf-gcc -v >>> Using built-in specs. >>> COLLECT_GCC=./xtensa-esp32-elf-gcc >>> COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper >>> Target: xtensa-esp32-elf >>> Configured with: >>> /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure >>> --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu >>> --target=xtensa-esp32-elf >>> --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf >>> --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf >>> --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include >>> --with-newlib --enable-threads=no --disable-shared >>> --with-pkgversion='crosstool-NG esp-2021r2' --disable-__cxa_atexit >>> --enable-cxx-flags=-ffunction-sections --disable-libgomp >>> --disable-libmudflap --disable-libmpx --disable-libssp >>> --disable-libquadmath --disable-libquadmath-support >>> --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >>> --enable-lto --enable-target-optspace --without-long-double-128 >>> --disable-nls --enable-multiarch --enable-languages=c,c++ >>> --disable-libstdcxx-verbose --enable-threads=posix >>> --enable-gcov-custom-rtio --enable-libstdcxx-time=yes >>> Thread model: posix >>> gcc version 8.4.0 (crosstool-NG esp-2021r2) >>> >>> >>> % ./riscv32-esp-elf-gcc -v >>> Using built-in specs. >>> COLLECT_GCC=./riscv32-esp-elf-gcc >>> COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/riscv32-esp-elf/esp-2021r2-8.4.0/riscv32-esp-elf/bin/../libexec/gcc/riscv32-esp-elf/8.4.0/lto-wrapper >>> Target: riscv32-esp-elf >>> Configured with: >>> /builds/idf/crosstool-NG/.build/riscv32-esp-elf/src/gcc/configure >>> --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu >>> --target=riscv32-esp-elf >>> --prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf >>> --with-local-prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf >>>
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hi Tomek, I think 6502 compiler are evolving, but I don't know if they are compatible. There is a interesting comparison here: https://gglabs.us/node/2293 CC. Gabriele here, since I don't know if here is in our list! BR, Alan On 10/8/22, Tomek CEDRO wrote: > By the way, I also found some tools for MOS6502 in the ports tree :-) > > # make quicksearch key="6502" > Port: acme-0.97.r319,1 > Path: /usr/ports/devel/acme > Info: Crossassembler for 6502, 65c02 and 65816 processors > > Port: cc65-2.19 > Path: /usr/ports/devel/cc65 > Info: Cross-compiler for 6502-based systems > > Port: dxa65-0.1.4 > Path: /usr/ports/devel/dxa65 > Info: Disassembler for MOS 6502 and compatible CPUs > > Port: vasm-1.8c > Path: /usr/ports/devel/vasm > Info: Portable 6502 6800 arm c16x jagrisc m68k ppc vidcore x86 z80 > assembler > > Port: xa65-2.3.11 > Path: /usr/ports/devel/xa65 > Info: Two-pass cross-assembler for MOS 6502 and compatible CPUs > > Port: p5-Acme-6502-0.77_2 > Path: /usr/ports/emulators/p5-Acme-6502 > Info: Pure Perl 65C02 simulator > > Port: nesasm-20040314_1 > Path: /usr/ports/lang/nesasm > Info: 6502 assembler with specific NES support > > > Not sure about dedicated toolchain for MC68000 (16-bit Atari and > Amiga) if there needs to be one or generic compiler can cross compile > that target.. but I will know that in some time as I have both Amiga > 600 and Atari ST Mega1 :-) > > Best regards :-) > Tomek > > > On Sat, Oct 8, 2022 at 3:15 PM Tomek CEDRO wrote: >> >> Well, toolchain is another thing on the BSD TODO list :-) You either >> need to have Espressif toolchain installed and in path or you can >> provide your own or system toolchain by hand durign build. >> >> I am on a trip right now with my backup laptop that is not my main >> development workstation, sorry, but the summary is below. >> >> 1. Because FreeBSD can natively emulate Linux ELF binaries, I did a >> trick with support of Espressif that allows download and install Linux >> tools on FreeBSD with ESP-IDF. That works fine.. but it would be >> perfect to build and distribute also toolchain binaries for FreeBSD by >> Espressif. So far I have used ESP IDF Linux tools on FreeBSD for >> initial experiments on ESP32 and ESP32-C3. >> >> % uname -a >> FreeBSD 0xCFMX4 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64 >> >> % ls -1 ~/.espressif/tools >> esp32s2ulp-elf >> esp32ulp-elf >> openocd-esp32 >> riscv32-esp-elf >> xtensa-esp32-elf >> xtensa-esp32s2-elf >> xtensa-esp32s3-elf >> >> That gives: >> >> % ./xtensa-esp32-elf-gcc -v >> Using built-in specs. >> COLLECT_GCC=./xtensa-esp32-elf-gcc >> COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper >> Target: xtensa-esp32-elf >> Configured with: >> /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure >> --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu >> --target=xtensa-esp32-elf >> --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf >> --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf >> --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include >> --with-newlib --enable-threads=no --disable-shared >> --with-pkgversion='crosstool-NG esp-2021r2' --disable-__cxa_atexit >> --enable-cxx-flags=-ffunction-sections --disable-libgomp >> --disable-libmudflap --disable-libmpx --disable-libssp >> --disable-libquadmath --disable-libquadmath-support >> --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools >> --enable-lto --enable-target-optspace --without-long-double-128 >> --disable-nls --enable-multiarch --enable-languages=c,c++ >> --disable-libstdcxx-verbose --enable-threads=posix >> --enable-gcov-custom-rtio --enable-libstdcxx-time=yes >> Thread model: posix >> gcc version 8.4.0 (crosstool-NG esp-2021r2) >> >> >> % ./riscv32-esp-elf-gcc -v >> Using built-in specs. >> COLLECT_GCC=./riscv32-esp-elf-gcc >> COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/riscv32-esp-elf/esp-2021r2-8.4.0/riscv32-esp-elf/bin/../libexec/gcc/riscv32-esp-elf/8.4.0/lto-wrapper >> Target: riscv32-esp-elf >> Configured with: >> /builds/idf/crosstool-NG/.build/riscv32-esp-elf/src/gcc/configure >> --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu >> --target=riscv32-esp-elf >> --prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf >> --with-local-prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf >> --with-headers=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf/include >> --with-newlib --enable-threads=no --disable-shared --with-arch=rv32imc >> --with-abi=ilp32 --with-pkgversion='crosstool-NG esp-2021r2' >>
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On Sat, Oct 8, 2022 at 3:28 PM Tomek CEDRO wrote: > (..) > Not sure about dedicated toolchain for MC68000 (16-bit Atari and > Amiga) if there needs to be one or generic compiler can cross compile > that target.. but I will know that in some time as I have both Amiga > 600 and Atari ST Mega1 :-) Okay, so I got information from PHK that MC68000 is handled directly by GCC (may require older version). If we take a look at gcc ports in the FreeBSD we have: % pkg search gcc aarch64-gcc12-12.1.0 Cross GNU Compiler Collection for aarch64 aarch64-gcc6-6.5.0_3 Cross GNU Compiler Collection for aarch64 aarch64-gcc9-9.5.0 Cross GNU Compiler Collection for aarch64 aarch64-none-elf-gcc-11.3.0GNU Compiler Collection for bare metal aarch64 cross-development afl++-gcc-4.00cFast instrumented fuzzer amd64-gcc12-12.1.0 Cross GNU Compiler Collection for amd64 amd64-gcc6-6.5.0_3 Cross GNU Compiler Collection for amd64 amd64-gcc9-9.5.0 Cross GNU Compiler Collection for amd64 arm-none-eabi-gcc-11.3.0 GNU Compiler Collection for bare metal arm cross-development arm-none-eabi-gcc492-4.9.2_5 GNU Compiler Collection for bare metal arm cross-development armv6-gcc12-12.1.0 Cross GNU Compiler Collection for armv6 armv6-gcc9-9.5.0 Cross GNU Compiler Collection for armv6 armv7-gcc12-12.1.0 Cross GNU Compiler Collection for armv7 armv7-gcc9-9.5.0 Cross GNU Compiler Collection for armv7 avr-gcc-11.2.0 FSF GCC for Atmel AVR 8-bit RISC cross-development colorgcc-1.4.5 Perl script to colorize the terminal output of GCC gcc-11_4 Meta-port for the default version of the GNU Compiler Collection gcc-arm-embedded-10.3.20210921 Complete gcc-based toolcahin for embedded ARM development gcc-ecj-4.5Eclipse Java Compiler used to build GCC Java gcc-msp430-ti-toolchain-9.3.1.2.20210722 Complete gcc-based toolcahin for TI MSP430 uC gcc10-10.4.0 GNU Compiler Collection 10 gcc11-11.3.0_1 GNU Compiler Collection 11 gcc11-devel-11.3.1.s20220930 GNU Compiler Collection 11 gcc12-12.2.0_2 GNU Compiler Collection 12 gcc12-devel-12.2.1.s20221001 GNU Compiler Collection 12 gcc13-devel-13.0.0.s20221002 GNU Compiler Collection 13 gcc48-4.8.5_14 GNU Compiler Collection 4.8 gcc6-aux-20180516_2,1 Version of GCC 6 with full Ada support gcc8-8.5.0_1 GNU Compiler Collection 8 gcc9-9.5.0 GNU Compiler Collection 9 gccmakedep-1.0.3 Create dependencies in makefiles using 'gcc -M' i386-gcc12-12.1.0 Cross GNU Compiler Collection for i386 i386-gcc6-6.5.0_3 Cross GNU Compiler Collection for i386 i386-gcc9-9.5.0Cross GNU Compiler Collection for i386 mingw32-gcc-4.8.1_5,1 FSF gcc-4 for Windows cross-development mips-gcc6-6.5.0_3 Cross GNU Compiler Collection for mips mips-gcc9-9.5.0Cross GNU Compiler Collection for mips mips64-gcc6-6.5.0_3Cross GNU Compiler Collection for mips64 mips64-gcc9-9.5.0 Cross GNU Compiler Collection for mips64 powerpc-gcc12-12.1.0 Cross GNU Compiler Collection for powerpc powerpc-gcc9-9.5.0 Cross GNU Compiler Collection for powerpc powerpc64-gcc12-12.1.0 Cross GNU Compiler Collection for powerpc64 powerpc64-gcc6-6.5.0_3 Cross GNU Compiler Collection for powerpc64 powerpc64-gcc9-9.5.0 Cross GNU Compiler Collection for powerpc64 py39-pygccxml-2.2.1Python package for easy C++ declarations navigation riscv32-unknown-elf-gcc-11.3.0 GNU Compiler Collection for bare metal riscv32 cross-development riscv64-gcc-8.3.0_1Cross GNU Compiler Collection for riscv64 riscv64-gcc12-12.1.0 Cross GNU Compiler Collection for riscv64 riscv64-gcc9-9.5.0 Cross GNU Compiler Collection for riscv64 riscv64-none-elf-gcc-11.3.0GNU Compiler Collection for bare metal riscv64 cross-development sparc64-gcc6-6.5.0_3 Cross GNU Compiler Collection for sparc64 sparc64-gcc9-9.5.0 Cross GNU Compiler Collection for sparc64 tigcc-0.96.b8_10 C compiler for the TI89, 92, and 92+ calculators zpu-gcc-1.0_1 ZPU gcc compiler Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
By the way, I also found some tools for MOS6502 in the ports tree :-) # make quicksearch key="6502" Port: acme-0.97.r319,1 Path: /usr/ports/devel/acme Info: Crossassembler for 6502, 65c02 and 65816 processors Port: cc65-2.19 Path: /usr/ports/devel/cc65 Info: Cross-compiler for 6502-based systems Port: dxa65-0.1.4 Path: /usr/ports/devel/dxa65 Info: Disassembler for MOS 6502 and compatible CPUs Port: vasm-1.8c Path: /usr/ports/devel/vasm Info: Portable 6502 6800 arm c16x jagrisc m68k ppc vidcore x86 z80 assembler Port: xa65-2.3.11 Path: /usr/ports/devel/xa65 Info: Two-pass cross-assembler for MOS 6502 and compatible CPUs Port: p5-Acme-6502-0.77_2 Path: /usr/ports/emulators/p5-Acme-6502 Info: Pure Perl 65C02 simulator Port: nesasm-20040314_1 Path: /usr/ports/lang/nesasm Info: 6502 assembler with specific NES support Not sure about dedicated toolchain for MC68000 (16-bit Atari and Amiga) if there needs to be one or generic compiler can cross compile that target.. but I will know that in some time as I have both Amiga 600 and Atari ST Mega1 :-) Best regards :-) Tomek On Sat, Oct 8, 2022 at 3:15 PM Tomek CEDRO wrote: > > Well, toolchain is another thing on the BSD TODO list :-) You either > need to have Espressif toolchain installed and in path or you can > provide your own or system toolchain by hand durign build. > > I am on a trip right now with my backup laptop that is not my main > development workstation, sorry, but the summary is below. > > 1. Because FreeBSD can natively emulate Linux ELF binaries, I did a > trick with support of Espressif that allows download and install Linux > tools on FreeBSD with ESP-IDF. That works fine.. but it would be > perfect to build and distribute also toolchain binaries for FreeBSD by > Espressif. So far I have used ESP IDF Linux tools on FreeBSD for > initial experiments on ESP32 and ESP32-C3. > > % uname -a > FreeBSD 0xCFMX4 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64 > > % ls -1 ~/.espressif/tools > esp32s2ulp-elf > esp32ulp-elf > openocd-esp32 > riscv32-esp-elf > xtensa-esp32-elf > xtensa-esp32s2-elf > xtensa-esp32s3-elf > > That gives: > > % ./xtensa-esp32-elf-gcc -v > Using built-in specs. > COLLECT_GCC=./xtensa-esp32-elf-gcc > COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper > Target: xtensa-esp32-elf > Configured with: > /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure > --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu > --target=xtensa-esp32-elf > --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf > --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf > --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include > --with-newlib --enable-threads=no --disable-shared > --with-pkgversion='crosstool-NG esp-2021r2' --disable-__cxa_atexit > --enable-cxx-flags=-ffunction-sections --disable-libgomp > --disable-libmudflap --disable-libmpx --disable-libssp > --disable-libquadmath --disable-libquadmath-support > --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools > --enable-lto --enable-target-optspace --without-long-double-128 > --disable-nls --enable-multiarch --enable-languages=c,c++ > --disable-libstdcxx-verbose --enable-threads=posix > --enable-gcov-custom-rtio --enable-libstdcxx-time=yes > Thread model: posix > gcc version 8.4.0 (crosstool-NG esp-2021r2) > > > % ./riscv32-esp-elf-gcc -v > Using built-in specs. > COLLECT_GCC=./riscv32-esp-elf-gcc > COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/riscv32-esp-elf/esp-2021r2-8.4.0/riscv32-esp-elf/bin/../libexec/gcc/riscv32-esp-elf/8.4.0/lto-wrapper > Target: riscv32-esp-elf > Configured with: > /builds/idf/crosstool-NG/.build/riscv32-esp-elf/src/gcc/configure > --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu > --target=riscv32-esp-elf > --prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf > --with-local-prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf > --with-headers=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf/include > --with-newlib --enable-threads=no --disable-shared --with-arch=rv32imc > --with-abi=ilp32 --with-pkgversion='crosstool-NG esp-2021r2' > --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections > --disable-libgomp --disable-libmudflap --disable-libmpx > --disable-libssp --disable-libquadmath --disable-libquadmath-support > --with-gmp=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools > --with-mpfr=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools > --with-mpc=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Well, toolchain is another thing on the BSD TODO list :-) You either need to have Espressif toolchain installed and in path or you can provide your own or system toolchain by hand durign build. I am on a trip right now with my backup laptop that is not my main development workstation, sorry, but the summary is below. 1. Because FreeBSD can natively emulate Linux ELF binaries, I did a trick with support of Espressif that allows download and install Linux tools on FreeBSD with ESP-IDF. That works fine.. but it would be perfect to build and distribute also toolchain binaries for FreeBSD by Espressif. So far I have used ESP IDF Linux tools on FreeBSD for initial experiments on ESP32 and ESP32-C3. % uname -a FreeBSD 0xCFMX4 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 GENERIC amd64 % ls -1 ~/.espressif/tools esp32s2ulp-elf esp32ulp-elf openocd-esp32 riscv32-esp-elf xtensa-esp32-elf xtensa-esp32s2-elf xtensa-esp32s3-elf That gives: % ./xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=./xtensa-esp32-elf-gcc COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/xtensa-esp32-elf/esp-2021r2-8.4.0/xtensa-esp32-elf/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper Target: xtensa-esp32-elf Configured with: /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include --with-newlib --enable-threads=no --disable-shared --with-pkgversion='crosstool-NG esp-2021r2' --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --enable-lto --enable-target-optspace --without-long-double-128 --disable-nls --enable-multiarch --enable-languages=c,c++ --disable-libstdcxx-verbose --enable-threads=posix --enable-gcov-custom-rtio --enable-libstdcxx-time=yes Thread model: posix gcc version 8.4.0 (crosstool-NG esp-2021r2) % ./riscv32-esp-elf-gcc -v Using built-in specs. COLLECT_GCC=./riscv32-esp-elf-gcc COLLECT_LTO_WRAPPER=/ztuff/cd/.espressif/tools/riscv32-esp-elf/esp-2021r2-8.4.0/riscv32-esp-elf/bin/../libexec/gcc/riscv32-esp-elf/8.4.0/lto-wrapper Target: riscv32-esp-elf Configured with: /builds/idf/crosstool-NG/.build/riscv32-esp-elf/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=riscv32-esp-elf --prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf --with-local-prefix=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf --with-headers=/builds/idf/crosstool-NG/builds/riscv32-esp-elf/riscv32-esp-elf/include --with-newlib --enable-threads=no --disable-shared --with-arch=rv32imc --with-abi=ilp32 --with-pkgversion='crosstool-NG esp-2021r2' --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --with-gmp=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools --with-mpfr=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools --with-mpc=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools --with-isl=/builds/idf/crosstool-NG/.build/riscv32-esp-elf/buildtools --enable-lto --enable-target-optspace --without-long-double-128 --disable-nls --enable-multiarch --enable-languages=c,c++ --disable-libstdcxx-verbose --enable-threads=posix --enable-gcov-custom-rtio --enable-libstdcxx-time=yes Thread model: posix gcc version 8.4.0 (crosstool-NG esp-2021r2) % ./openocd -v Open On-Chip Debugger v0.10.0-esp32-20210902 (2021-09-02-09:38) 2. FreeBSD has its own ports and packages with various build toolchains for almost any target out there. For NuttX you need to provide desired toolchain by hand for now but I would like to add this to configure / KConfig so it gets auto-configured to use OS defaults :-) Some examples with versions below :-) % pkg search riscv riscv-isa-sim-g_20211015 Spike, a RISC-V ISA Simulator riscv32-unknown-elf-binutils-2.37_4,1 GNU binary tools riscv32-unknown-elf-gcc-11.3.0 GNU Compiler Collection for bare metal riscv32 cross-development riscv64-binutils-2.37_4,1 GNU binary tools riscv64-freebsd-sysroot-a2021.11.09 FreeBSD 13.0-RELEASE riscv64 sysroot riscv64-gcc-8.3.0_1Cross GNU Compiler Collection for riscv64 riscv64-gcc12-12.1.0 Cross GNU Compiler Collection for riscv64 riscv64-gcc9-9.5.0 Cross GNU Compiler Collection for riscv64
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Thank you very much Tomek! when you get NuttX compiled on FreeBSD, please run the similar commands like these: $ xtensa-esp32-elf-gcc -v Using built-in specs. COLLECT_GCC=xtensa-esp32-elf-gcc COLLECT_LTO_WRAPPER=/usr/local/bin/../libexec/gcc/xtensa-esp32-elf/8.4.0/lto-wrapper Target: xtensa-esp32-elf Configured with: /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/gcc/configure --build=x86_64-build_pc-linux-gnu --host=x86_64-build_pc-linux-gnu --target=xtensa-esp32-elf --prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf --with-local-prefix=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf --with-headers=/builds/idf/crosstool-NG/builds/xtensa-esp32-elf/xtensa-esp32-elf/include --with-newlib --enable-threads=no --disable-shared --with-pkgversion='crosstool-NG esp-2021r2-patch3' --disable-__cxa_atexit --enable-cxx-flags=-ffunction-sections --disable-libgomp --disable-libmudflap --disable-libmpx --disable-libssp --disable-libquadmath --disable-libquadmath-support --with-gmp=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpfr=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-mpc=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --with-isl=/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/buildtools --enable-lto --enable-target-optspace --without-long-double-128 --disable-nls --enable-multiarch --enable-languages=c,c++ --disable-libstdcxx-verbose --enable-threads=posix --enable-gcov-custom-rtio --enable-libstdcxx-time=yes Thread model: posix gcc version 8.4.0 (crosstool-NG esp-2021r2-patch3) If you send just the last line above it fine, we only need to know the toolchain version and characteristic. $ xtensa-esp32-elf-size nuttx textdata bss dec hex filename 75231 3207736 83287 14557 nuttx BR, Alan On 10/8/22, Tomek CEDRO wrote: > Hey there Alan :-) > > I am working on FreeBSD / BSD: > 1. kconfig-frontends is now in the FreeBSD ports and packages. > 2. I need to fix the SEDvsGSED issue. > 3. Have some ideas on how to unify MAKEvsGMAKE. > 4. KConfig work to add BSD also needs to be done. > 5. All 2 to 4 would point to GNUvsBSD build tools unification so > things work out of the box on both GNU and BSD in the same way with no > local modifications. > > This is not yet into this release, but lots of other work is done, and > this seems to be a release that others also wait to go out in order to > add their patches.. thus +1 from me not to block the works.. otherwise > no rush from me as things are done when they are done :-) > > Best regards :-) > Tomek > > > > > > On Sat, Oct 8, 2022 at 1:37 PM Alan C. Assis wrote: >> >> Hi everyone, >> >> As suggestion when voting for a new release, please send together the >> information about what compiler was used and the output of your >> toolchain "size". >> >> This is just a suggestion, but help us to know that you really tested >> the release and also it is used as reference to know if the size >> increased too much or if there is some discrepancies between different >> toolchains. >> >> Thank you for understanding. >> >> BR, >> >> Alan >> >> On 10/8/22, Tomek CEDRO wrote: >> > +1 from me :-) >> > >> > -- >> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >> > > > > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hey there Alan :-) I am working on FreeBSD / BSD: 1. kconfig-frontends is now in the FreeBSD ports and packages. 2. I need to fix the SEDvsGSED issue. 3. Have some ideas on how to unify MAKEvsGMAKE. 4. KConfig work to add BSD also needs to be done. 5. All 2 to 4 would point to GNUvsBSD build tools unification so things work out of the box on both GNU and BSD in the same way with no local modifications. This is not yet into this release, but lots of other work is done, and this seems to be a release that others also wait to go out in order to add their patches.. thus +1 from me not to block the works.. otherwise no rush from me as things are done when they are done :-) Best regards :-) Tomek On Sat, Oct 8, 2022 at 1:37 PM Alan C. Assis wrote: > > Hi everyone, > > As suggestion when voting for a new release, please send together the > information about what compiler was used and the output of your > toolchain "size". > > This is just a suggestion, but help us to know that you really tested > the release and also it is used as reference to know if the size > increased too much or if there is some discrepancies between different > toolchains. > > Thank you for understanding. > > BR, > > Alan > > On 10/8/22, Tomek CEDRO wrote: > > +1 from me :-) > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Hi everyone, As suggestion when voting for a new release, please send together the information about what compiler was used and the output of your toolchain "size". This is just a suggestion, but help us to know that you really tested the release and also it is used as reference to know if the size increased too much or if there is some discrepancies between different toolchains. Thank you for understanding. BR, Alan On 10/8/22, Tomek CEDRO wrote: > +1 from me :-) > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
+1 from me :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On Fri, Oct 7, 2022 at 1:04 PM TimH wrote: > >I'm assuming I have to have subscribed to that mailing list to vote so I just > >have, but it is not clear from the welcome email received how to actually get > >the relevant mail from Alin downloaded so I can reply? Looks like I need a > >message ID to get it, but can't see message IDS anywhere? Assuming that is > >the way to do this? I don't think you have to be subscribed; AFAIK anyone should be able to email gene...@incubator.apache.org (and most if not all mailing lists) though if you're not subscribed then you'd have to ask people to CC you on any responses and then hopefully they do... > OK - found the ID by looking at the raw email on the lists.apache.org > webpage...requested it by email...answer received with Alin's email attached > but the actual body text is completely missing. But replied anyway, pasting a > small snip of text to give it context! Great! I can confirm I see it and it shows up as a reply to that thread, so looks like that In-Reply-To trick worked. :-) Thanks for helping! Nathan
RE: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
>From: TimH >Sent: 07 October 2022 17:45 >To: dev@nuttx.apache.org >Subject: RE: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2] > >>-Original Message- >>From: Nathan Hartman >>Sent: 07 October 2022 17:28 >> >>On Fri, Oct 7, 2022 at 11:10 AM TimH wrote: >>> >>> Would you still like another non-binding +1 vote? >>> >>> I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom >>> board >>and have successfully built and run a Nuttx shell (after a few changes >>to my custom make.defs). >> >>This vote (in the NuttX PPMC, i.e., dev@nuttx.apache.org) passed, but >>since we're an incubating project (until we graduate), we need a second >>round of voting in the Apache.org IPMC (i.e., >>gene...@incubator.apache.org)... That vote has not closed yet and, yes, >>we would like all the attention we could get on it!! >> >>Let me find that vote thread >> >>Here it is: >>https://lists.apache.org/thread/0h6wq2cqk3ckdttz78964fw4007b51lr >> >>Let us know if you need anything! >> >I'm assuming I have to have subscribed to that mailing list to vote so I just >have, but it is not clear from the welcome email received how to actually get >the relevant mail from Alin downloaded so I can reply? Looks like I need a >message ID to get it, but can't see message IDS anywhere? Assuming that is >the way to do this? OK - found the ID by looking at the raw email on the lists.apache.org webpage...requested it by email...answer received with Alin's email attached but the actual body text is completely missing. But replied anyway, pasting a small snip of text to give it context!
RE: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
>-Original Message- >From: Nathan Hartman >Sent: 07 October 2022 17:28 > >On Fri, Oct 7, 2022 at 11:10 AM TimH wrote: >> >> Would you still like another non-binding +1 vote? >> >> I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom board >and have successfully built and run a Nuttx shell (after a few changes to my >custom make.defs). > >This vote (in the NuttX PPMC, i.e., dev@nuttx.apache.org) passed, but since >we're an incubating project (until we graduate), we need a second round of >voting in the Apache.org IPMC (i.e., gene...@incubator.apache.org)... That >vote has not closed yet and, yes, we would like all the attention we could get >on it!! > >Let me find that vote thread > >Here it is: >https://lists.apache.org/thread/0h6wq2cqk3ckdttz78964fw4007b51lr > >Let us know if you need anything! > I'm assuming I have to have subscribed to that mailing list to vote so I just have, but it is not clear from the welcome email received how to actually get the relevant mail from Alin downloaded so I can reply? Looks like I need a message ID to get it, but can't see message IDS anywhere? Assuming that is the way to do this?
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On Fri, Oct 7, 2022 at 12:27 PM Nathan Hartman wrote: > > On Fri, Oct 7, 2022 at 11:10 AM TimH wrote: > > > > Would you still like another non-binding +1 vote? > > > > I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom board and > > have successfully built and run a Nuttx shell (after a few changes to my > > custom make.defs). > > This vote (in the NuttX PPMC, i.e., dev@nuttx.apache.org) passed, but > since we're an incubating project (until we graduate), we need a > second round of voting in the Apache.org IPMC (i.e., > gene...@incubator.apache.org)... That vote has not closed yet and, > yes, we would like all the attention we could get on it!! > > Let me find that vote thread > > Here it is: https://lists.apache.org/thread/0h6wq2cqk3ckdttz78964fw4007b51lr > > Let us know if you need anything! > > Cheers, > Nathan Forgot to say: When you vote, please write "(non-binding)" -- unless you're a member of the Incubator PMC (IPMC) of course! Even if the vote is non-binding, it still attracts attention to the project and may help us get some binding votes from IPMC members. (I heard that quite a few of the IPMC mentors are at Apachecon and that has been delaying things like votes as well as sign-offs on board reports. So hopefully in the next few days the situation will improve.) Cheers, Nathan
Re: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
On Fri, Oct 7, 2022 at 11:10 AM TimH wrote: > > Would you still like another non-binding +1 vote? > > I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom board and > have successfully built and run a Nuttx shell (after a few changes to my > custom make.defs). This vote (in the NuttX PPMC, i.e., dev@nuttx.apache.org) passed, but since we're an incubating project (until we graduate), we need a second round of voting in the Apache.org IPMC (i.e., gene...@incubator.apache.org)... That vote has not closed yet and, yes, we would like all the attention we could get on it!! Let me find that vote thread Here it is: https://lists.apache.org/thread/0h6wq2cqk3ckdttz78964fw4007b51lr Let us know if you need anything! Cheers, Nathan
RE: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2]
Would you still like another non-binding +1 vote? I just merged 11.0.0 [RC2] into my 10.3 endeavours with my custom board and have successfully built and run a Nuttx shell (after a few changes to my custom make.defs). >-Original Message- >From: Alin Jerpelea >Sent: 22 September 2022 13:20 >To: dev@nuttx.apache.org >Subject: [RESULT] Release Apache NuttX (Incubating) 11.0.0 [RC2] > >Hi, > >The vote closes now as over 72hr have passed. The vote PASSES with 3 >(+3 non-binding) votes from the PPMC, >0 (+1 binding) vote from the IPMC, >3 (+0 non-binding) votes from the developer community, No further +1, 0 or - >1 votes. > >The vote thread: >[1]https://lists.apache.org/thread/rv9pf8gtbcq4zjnydv2h2lsymszzb33f > >I will now bring the vote to gene...@incubator.apache.org to get approval by >the IPMC. >If this vote passes also, the release is accepted and will be published. > >Thanks, >Alin Jerpelea
