Re: Podling Nuttx Report Reminder - July 2022
On Tue, Jun 28, 2022 at 10:03 PM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 20 July 2022. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, July 06). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://cwiki.apache.org/confluence/display/INCUBATOR/July2022 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Note: The format of the report has changed to use markdown. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC > Just a reminder I copied our report to the Incubator report. Mentors, please review and sign off!! Cheers Nathan
Podling Nuttx Report Reminder - July 2022
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 July 2022. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, July 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/July2022 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: net/if_arp.h - standard header?
On Tue, Jun 28, 2022 at 4:05 PM Nathan Hartman wrote: > > I have a program that builds under Linux, BSD, and macOS which > includes the net/if_arp.h header. > > This header does not seem to exist under NuttX. > > It is included for the ARPHRD_ETHER define (and possibly other things). > > I see that under NuttX, this is defined in net/arp.h, rather than > net/if_arp.h. > > Is net/if_arp.h supposed to be a standard header? I cannot seem to > find any meaningful information about it. > > Thanks, > Nathan Also, do we lack the defines IFF_LOOPBACK, IFF_UP, IFF_BROADCAST, and IFF_MULTICAST? I can't find them anywhere, except in comments. For example, a grep for IFF_LOOPBACK shows it in the comments for getifaddrs(): [[[ * Depending on whether the bit IFF_BROADCAST or IFF_POINTOPOINT is * set in ifa_flags (only one can be set at a time), either * ifa_broadaddr will contain the broadcast address associated with * ifa_addr (if applicable for the address family) or ifa_dstaddr * will contain the destination address of the point-to-point * interface. ]]] but no such define exists in NuttX.
net/if_arp.h - standard header?
I have a program that builds under Linux, BSD, and macOS which includes the net/if_arp.h header. This header does not seem to exist under NuttX. It is included for the ARPHRD_ETHER define (and possibly other things). I see that under NuttX, this is defined in net/arp.h, rather than net/if_arp.h. Is net/if_arp.h supposed to be a standard header? I cannot seem to find any meaningful information about it. Thanks, Nathan
RE: [ANNOUNCE] Apache NuttX 10.3.0-incubating released
My plan is to start the release process every 3 moths Best regards Alin -Original Message- From: Abdelatif Guettouche Sent: den 24 juni 2022 13:16 To: dev@nuttx.apache.org Subject: Re: [ANNOUNCE] Apache NuttX 10.3.0-incubating released > What are next steps? Release wise, nothing -- we just need to keep making releases. For graduation that's a different story that we need to discuss. There is a checklist here: https://urldefense.com/v3/__https://incubator.apache.org/guides/graduation.html*before_you_graduate__;Iw!!JmoZiZGBv3RvKRSx!8tn0GIg4ZXCYp5d7w2Ddmz46Ru5vu3M9l7ITUE-sm8dUxgKagg6sUU42BoQpzvacM_TrGnk7QuEv-cb3y2U-9fSPwKfp$ I believe we already checked most of the boxes. On Fri, Jun 24, 2022 at 12:43 PM Alan Carvalho de Assis wrote: > > Very nice! Kudo guys! > > What are next steps? > > BR, > > Alan > > On Friday, June 24, 2022, Abdelatif Guettouche < > abdelatif.guettou...@gmail.com> wrote: > > > First non-WIP release! One step closer to graduation! > > > > On Fri, Jun 24, 2022 at 7:47 AM Tomek CEDRO wrote: > > > > > > CONGRATZ! :-) > > > > > > -- > > > CeDeROM, SQ7MHZ, > > > https://urldefense.com/v3/__http://www.tomek.cedro.info__;!!JmoZiZ > > > GBv3RvKRSx!8tn0GIg4ZXCYp5d7w2Ddmz46Ru5vu3M9l7ITUE-sm8dUxgKagg6sUU4 > > > 2BoQpzvacM_TrGnk7QuEv-cb3y2U-9VE5857q$ > >
Re: [DISCUSS] Graduate NuttX as TLP
Yes, a lot of files with hyphen: $ find . -name "*-*" ./arch/z80/src/ez80/clang-compat.asm ./arch/xtensa/include/esp32s2/core-isa.h ./arch/xtensa/include/esp32s2/tie-asm.h ./arch/xtensa/include/esp32/core-isa.h ./arch/xtensa/include/esp32/tie-asm.h ./arch/xtensa/include/esp32s3/core-isa.h ./arch/xtensa/include/esp32s3/tie-asm.h ./arch/sparc/src/bm3803/bm3803-timerisr.c ./arch/sparc/src/bm3803/bm3803-lowconsole.c ./arch/sparc/src/bm3803/bm3803-config.h ./arch/sparc/src/bm3803/bm3803-lowinit.c ./arch/sparc/src/bm3803/bm3803-memorymap.h ./arch/sparc/src/bm3803/bm3803-serial.c ./arch/sparc/src/bm3803/bm3803-irq.c ./arch/sparc/src/bm3803/bm3803-uart.h ./arch/sparc/src/bm3823/bm3823-serial.c ./arch/sparc/src/bm3823/bm3823-uart.h ./arch/sparc/src/bm3823/bm3823-lowconsole.c ./arch/sparc/src/bm3823/bm3823-timerisr.c ./arch/sparc/src/bm3823/bm3823-memorymap.h ./arch/sparc/src/bm3823/bm3823-irq.c ./arch/sparc/src/bm3823/bm3823-config.h ./arch/sparc/src/bm3823/bm3823-lowinit.c ./arch/sim/src/nuttx-names.in ./arch/risc-v ./arch/risc-v/src/qemu-rv ./arch/risc-v/include/qemu-rv ./arch/arm/src/armv8-m ./arch/arm/src/armv7-r ./arch/arm/src/armv7-a ./arch/arm/src/armv6-m ./arch/arm/src/armv7-m ./arch/arm/include/armv8-m ./arch/arm/include/armv7-r ./arch/arm/include/armv7-a ./arch/arm/include/armv6-m ./arch/arm/include/armv7-m ./arch/mips/src/mips32/mips32-memorymap.h ./Documentation/contributing/making-changes.rst ./Documentation/platforms/xtensa/esp32/boards/esp32-devkitc ./Documentation/platforms/xtensa/esp32/boards/esp32-devkitc/esp32-core-board-v2.jpg ./Documentation/platforms/xtensa/esp32/boards/esp32-devkitc/esp32-devkitc-v4-front.jpg ./Documentation/platforms/xtensa/esp32/boards/esp32-wrover-kit ./Documentation/platforms/xtensa/esp32/boards/esp32-wrover-kit/esp-wrover-kit-v4.1-layout-back.png ./Documentation/platforms/xtensa/esp32/boards/esp32-wrover-kit/esp-wrover-kit-v4.1-layout-front.png ./Documentation/platforms/xtensa/esp32s3/boards/esp32s3-devkit ./Documentation/platforms/xtensa/esp32s3/boards/esp32s3-devkit/esp32-s3-devkitc-1.png ./Documentation/platforms/xtensa/esp32s3/boards/esp32s3-eye ./Documentation/platforms/risc-v ./Documentation/platforms/risc-v/esp32c3/boards/esp32c3-devkit ./Documentation/platforms/risc-v/esp32c3/boards/esp32c3-devkit/ESP32-C3-DevKitM-1-v1.0.png ./Documentation/platforms/risc-v/esp32c3/boards/esp32c3-devkit/ESP32-C3-DevKitC-02-v1.1.png ./Documentation/platforms/arm/stm32wl5/boards/nucleo-wl55jc ./Documentation/platforms/arm/imxrt/boards/imxrt1060-evk ./Documentation/platforms/arm/imxrt/boards/imxrt1060-evk/imxrt1060-evk-front.jpg ./Documentation/platforms/arm/imxrt/boards/imxrt1020-evk ./Documentation/platforms/arm/imxrt/boards/imxrt1064-evk ./Documentation/platforms/arm/imxrt/boards/teensy-4.x ./Documentation/platforms/arm/imxrt/boards/imxrt1050-evk ./Documentation/platforms/arm/nrf52/boards/nrf52832-sparkfun ./Documentation/platforms/arm/nrf52/boards/nrf52832-mdk ./Documentation/_static/images/menuconfig-debug.png ./Documentation/guides/image/syscall-protected-before.png ./Documentation/guides/image/syscall-protected-after.png ./Documentation/guides/image/syscall-flat-after.png ./Documentation/guides/image/trace-compass-screenshot.png ./Documentation/guides/image/syscall-flat-before.png ./Documentation/guides/image/task-trace-internal.png ./Documentation/guides/image/task-trace-overview.png ./boards/xtensa/esp32s2/esp32s2-saola-1 ./boards/xtensa/esp32s2/esp32s2-saola-1/src/esp32s2-saola-1.h ./boards/xtensa/esp32/esp32-devkitc ./boards/xtensa/esp32/esp32-devkitc/src/esp32-devkitc.h ./boards/xtensa/esp32/esp32-wrover-kit ./boards/xtensa/esp32/esp32-wrover-kit/src/esp32-wrover-kit.h ./boards/xtensa/esp32/esp32-ethernet-kit ./boards/xtensa/esp32/esp32-ethernet-kit/src/esp32-ethernet-kit.h ./boards/xtensa/esp32s3/esp32s3-devkit ./boards/xtensa/esp32s3/esp32s3-devkit/src/esp32s3-devkit.h ./boards/xtensa/esp32s3/esp32s3-eye ./boards/xtensa/esp32s3/esp32s3-eye/src/esp32s3-eye.h ./boards/x86_64/intel64/qemu-intel64 ./boards/x86/qemu/qemu-i486 ./boards/avr/atmega/moteino-mega ./boards/avr/atmega/arduino-mega2560 ./boards/avr/at90usb/teensy-2.0 ./boards/avr/at90usb/teensy-2.0/src/teensy-20.h ./boards/z16/z16f/z16f2800100zcog/tools/zneo-zdsii-5_0_1-variadic-func-fix.patch ./boards/renesas/rx65n/rx65n-rsk1mb ./boards/renesas/rx65n/rx65n-rsk2mb ./boards/renesas/rx65n/rx65n-grrose ./boards/sim/sim/sim/NETWORK-VPNKIT.txt ./boards/sim/sim/sim/NETWORK-LINUX.txt ./boards/hc/m9s12/ne64badge/scripts/ne64badge-nonbanked.ld ./boards/hc/m9s12/ne64badge/scripts/ne64badge-banked.ld ./boards/hc/m9s12/demo9s12ne64/scripts/demo9s12ne64-banked.ld ./boards/hc/m9s12/demo9s12ne64/scripts/demo9s12ne64-unbanked.ld ./boards/risc-v ./boards/risc-v/mpfs/m100pfsevp/scripts/user-space.ld ./boards/risc-v/mpfs/m100pfsevp/scripts/ld-envm.script ./boards/risc-v/mpfs/m100pfsevp/scripts/hss-nuttx.yml ./boards/risc-v/mpfs/icicle/scripts/user-space.ld ./boards/risc-v/mpfs/icicle/scripts/kernel-space.ld
Re: [DISCUSS] Graduate NuttX as TLP
The ZiLOG tools won't accept a hyphen in file names either This problem exists for other directories and files that include a hypen in the name. There have been several PRs changing file/directory names to use an underscore instead of a hyphen.
Re: [DISCUSS] Graduate NuttX as TLP
I also prefer '-' character but after some adventures with crazy JavaScript world I have switched to '_' as it treated part of the string as mathematical subtraction operation on the string lol :-) :-) :-) I never had this problem with C or Python so we should be safe here :-) :-) The ZiLOG tools won't accept a hyphen in file names either. There are also quirks with use of hyphens in filenames. For example, the first character of a filename cannot be a hyphen. I think that there are some old, obsolete file systems that won't accept a hyphen in a filename either.
Re: [DISCUSS] Graduate NuttX as TLP
Agree! nuttx_apps is better :-) BR, Alan On Tuesday, June 28, 2022, Tomek CEDRO wrote: > On Tue, Jun 28, 2022 at 9:50 AM Sebastien Lorquet wrote: > > if I can express my taste on this extra minor choice I think nuttx-apps > > looks better than nuttx_apps > > I also prefer '-' character but after some adventures with crazy > JavaScript world I have switched to '_' as it treated part of the > string as mathematical subtraction operation on the string lol :-) :-) > :-) > > I never had this problem with C or Python so we should be safe here :-) :-) > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info >
Re: [DISCUSS] Graduate NuttX as TLP
On Tue, Jun 28, 2022 at 9:50 AM Sebastien Lorquet wrote: > if I can express my taste on this extra minor choice I think nuttx-apps > looks better than nuttx_apps I also prefer '-' character but after some adventures with crazy JavaScript world I have switched to '_' as it treated part of the string as mathematical subtraction operation on the string lol :-) :-) :-) I never had this problem with C or Python so we should be safe here :-) :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [DISCUSS] Graduate NuttX as TLP
hi, yes, this solution "just" requires a sed on all defconfig files, and avoids having to specify the directory name in the git clone command, which can easily be forgotten. if I can express my taste on this extra minor choice I think nuttx-apps looks better than nuttx_apps Sebastien On 6/28/22 06:15, alin.jerpe...@sony.com wrote: I think that we should modify the paths so that we use nuttx and nuttx_apps folders. In my opinion this will be less confusing for the users Best regards Alin -Original Message- From: Tomek CEDRO Sent: den 28 juni 2022 02:55 To: dev@nuttx.apache.org Subject: Re: [DISCUSS] Graduate NuttX as TLP Congratulations on NuttX Graduation and all of the achievements! :-) On Mon, Jun 27, 2022 at 6:18 PM Alan Carvalho de Assis wrote: I don't know you guys but I hate this incubator-nuttx and incubator-nuttx-apps repositories names. I hope we get github.com/apache/nuttx and github.com/apache/apps soon (hope they accept we use this /apps name, will make our users life easier!) +1 :-) How about something like nuttx_rtos and nuttx_apps ? It was not clear for me what apps are and if they are mandatory.. keeping apache/apps could be even more confusing.. also I usually keep `.git` suffix for directories that keep git repos and that was not working here :-) Maybe just nuttx + nuttx/nuttx_apps where apps are git submodule kept as it is right now in a sperate repo for easier maintenance? :-) -- CeDeROM, SQ7MHZ, https://urldefense.com/v3/__http://www.tomek.cedro.info__;!!JmoZiZGBv3RvKRSx!6HrO-4qVO1mY_faiW-6kxCv6sQxyeUdYuL9_HLWZCaxV9eclVaPiUFuThqR-7C8RXGs6X-G2MtYdfE46lg$
