Re: NuttX 9.X C++11 Support

Use of newlib with NuttX should be avoid.  It is not binary compatible with NuttX.  See https://cwiki.apache.org/confluence/display/NUTTX/Integrating+with+Newlib This should be used instead: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139629545 On 6/19/2020 3:54 PM,

Re: The new Apache NuttX Logo

When we talk about logos and mascots, we also need to be concerned about infringing on trademarks.  When this gets down to a few candidates we will probably need to do some investigation to make sure that we do have the rights to use the mascot.

Re: The new Apache NuttX Logo

I once was told that it was Linus Torvalds who insisted on the Pengquin mascot.  My favorit animal, my "totem animal" is  turtle. Unfortunately, a turtle is not a good representation for a real time operating system!  Unless it were a Mutant Ninja turtle ;) NuttX is a very international

Re: NXView

The major differences are: - Different trace data format between the accumulated data in the memory and /dev/tracer output It is because to reduce the trace data size in the memory. The accumulated data contains packed (not aligned) values and task is recorded by its PID, not the

Re: NXView

into the different PRs: - remaining system call trace support code which requires the modification to the build system - sched tracer and device driver which uses new sched note APIs (needs more discussion) Thanks, Yuuichi Nakamura -Original Message- From: Gregory Nutt Sent: Tuesday, June

Re: nrf51822 and BLE

AFAIK NuttX supports the Host level API and at most HCI UART interface. I'm referring to the link-level code which interfaces directly with NRF51822 so that you can run NuttX in the board itself (and not as an external module via UART). It supports both host and slave and uses a driver

Re: NXView

eg Regardless of that decision, it would be nice if you could at least upstream the interrupt and system call instrumentation. That will be needed in any event and we should re-use that logic, not re-invent it. I did that.  I created PR 1256 with the commit in your name

Re: NXView

Hi, Greg. I am developing the feature to collect the NuttX internal task events and dump the data in Linux ftrace format. The dumped data can be displayed graphically by using "TraceCompass". It extends the NuttX sched note APIs to get enter/leave event of the interrupt handler and system

Re: NXView

Hi, Greg. I am developing the feature to collect the NuttX internal task events and dump the data in Linux ftrace format. The dumped data can be displayed graphically by using "TraceCompass". It extends the NuttX sched note APIs to get enter/leave event of the interrupt handler and system

Re: NXView

In the past NuttX used to have a Buildroot that was able to generate the toolchain, etc. It is still around, some time ago David Alessio fixed it. It generates more than that.  It generates most of the tools that you need including kconfig-frontends, genromfs, etc.  And it is easily

Re: [nuttx] Re: NXView

You sucked me in. It was only $8 to get one here tomorrow... and I am not sure I can find another use for it even if this does not work out. For those following along, you can find the board I am talking about on ebay, amazon, etc.. by looking for "EX-USB FX2LP" I ordered a couple of those

Re: [nuttx] Re: NXView

On 6/13/2020 3:25 PM, Brennan Ashton wrote: On Sat, Jun 13, 2020 at 1:56 PM Gregory Nutt wrote: The problem is that in the context of the OS instrumentation call-outs, we can do no driver operations. With the FT245R, it could do writes to a memory-mapped FIFO. Most of the FX2LP modes

Re: [nuttx] Re: NXView

Makes total sense if it provides enough bandwidth. There are some other options that are based off of the FX2 USB2.0 chip that are common in low cost ($10) 8ch 25MHZ logic analyzers as well. As you said it's a block with a few input pins, FIFO, and a usb interface, so if it works, sounds

Re: [nuttx] Re: NXView

If you want high-speed io to USB the FX3 is probably one of the best bets. You see it frequently used on logic analyser and software defined radio boards between the USB and the FPGA. https://www.cypress.com/products/ez-usb-fx3-superspeed-usb-30-peripheral-controller There are several

Re: [nuttx] Re: NXView

Thanks, Brennan and Petr, for the recommendations. At this point, I am only trying to ascertain if there are a few people interested in participating in such a project.  I think it is more that I can consider to do alone so any further steps would require some interest in the development

Re: NXView

a-oriented language used in the data sheets? If you know something about these options, I would like to hear from you. Greg On 6/12/2020 6:02 PM, Gregory Nutt wrote: Hi, List, I have been contemplating a NuttX-based Open Source project today and I am interested in seeing if anyone

NXView

Hi, List, I have been contemplating a NuttX-based Open Source project today and I am interested in seeing if anyone is willing to participate or, even if not, if anyone has any insights or recommendations that could be useful. Basically, I am thinking of a NuttX tool to monitor the internal

Re: [nuttx] Apache and BSD license compatibility

I just noticed that this conversation was occurring on nu...@googlegroups.com.  Not sure how we got there.  Moving back to dev@nuttx.apache.org where I thought we were all along. There is one big difference.  I have spoken (via email) with all of the authors and copyright holders and each has

Re: [nuttx] Apache and BSD license compatibility

I just noticed that this conversation was occurring on nu...@googlegroups.com.  Not sure how we got there.  Moving back to dev@nuttx.apache.org where I thought we were all along. There is one big difference. I have spoken (via email) with all of the authors and copyright holders and each has

Re: SAMA5D27 SDMMC support branch

I'm talking about using drivers from the OpenBSD or FreeBSD projects, not the driver on Github. :) There is a partial port of the OpenBSD IEEE802.11 SoftMAC stack that I did a long time ago here too: https://github.com/gregory-nutt/nuttx_ieee80211

Re: SAMA5D27 SDMMC support branch

I'm talking about using drivers from the OpenBSD or FreeBSD projects, not the driver on Github. :) Okay This page on the Apache website is pretty clear that BSD licensed code may be included in an Apache project. The

Re: SAMA5D27 SDMMC support branch

This page on the Apache website is pretty clear that BSD licensed code may be included in an Apache project. But, unfortunately, that driver on github is GPL.

Re: SAMA5D27 SDMMC support branch

54 Mbps would work for me. But I didn't see a LICENSE file or any text about it in the README file either in that repo. So I'm assuming this is not a driver that can be used. Or else it needs some work with Microchip to get them to clarify the license. Re: using a BSD driver, I didn't get

Re: SAMA5D27 SDMMC support branch

Re: using a BSD driver, I didn't get what you mean about bringing in 3rd party code– it's BSD licensed, my understanding is that it can be brought in. Is that wrong? You will need to discuss with Justin.  We have talked about this numerous times and still don't have any idea what is

Re: SAMA5D27 SDMMC support branch

Hey, SAMA5D2 guys, I have been looking at the ATSAMA5D27-WLSOM1 Evaluation Kit.  I am impressed.  It is based on the SAMAD27C and the ATWIL3000 wireless module.  I am tempted to buy one. The ATWIL3000 has an SDIO interface to the Wifi (like the Broadcom chips) and UART interface to the

New Wiki Page

Why Can't Kernel Threads Have pthreads? https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158862687

Re: Reduced Participation

On 6/8/2020 2:07 AM, Matous Pokorny wrote: +1, thank you very much for hard work po 8. 6. 2020 v 7:39 odesílatel Alin Jerpelea napsal: Thanks for all your hard work and patience. Alin Thanks, guys.  What a long strange trip its been!

[OT] Linux Sucks

Linux Sucks 2020: https://www.youtube.com/watch?v=cZN5n6C9gM4=youtu.be Lots of good thoughts in that presentation for ALL open source projects.  Long, but well worth the time.

Re: [DISCUSS] requirements for commit messages and PRs

But I think it would help to stop call then by judgmental names. You mean like referring to me as the guy with the "lack of working project experience and vision" .  You made this personal. What do you expect then?  Courtesy for your stupid ideas?

Re: [DISCUSS] requirements for commit messages and PRs

But I think it would help to stop call then by judgmental names. You mean like referring to me as the guy with the "lack of working project experience and vision" .  You made this personal.

Re: [DISCUSS] requirements for commit messages and PRs

But I think it would help to stop call then by judgmental names. Unless of course the final one will be god-wonderful :) Are you implying we should accept that crap with no judgement? Doesn't work that way.  That old template was crap and everyone knows it.  I have no problem judging

Re: [DISCUSS] requirements for commit messages and PRs

But I think it would help to stop call then by judgmental names. Unless of course the final one will be god-wonderful :) Are you implying we should accept that crap with no judgement? Doesn't work that way.  That old template was crap and everyone knows it.  I have no problem judging it. 

Re: [DISCUSS] requirements for commit messages and PRs

About unilateral decisions: We should not make them. We need to discuss and vote on things. The vote will be interesting.  What will be the two options?  The current template or that god-awful one we had for a few days?  Is that what we would be voting on?

Re: [DISCUSS] requirements for commit messages and PRs

Very good points there. I like the idea of making it a collaborative effort between the contributors and the reviewers. It is a courtesy of the contributor to make their code available to the world.  It is the responsibility of the reviewer/committer to assure that there is sufficient

Re: [DISCUSS] requirements for commit messages and PRs

Yes. Simplicity is single most important thing. The entire template should fit entirely within the PR comment window. It should not be a punishment to contributors to the project. We will get a better response if it is simple and usable. No inline instructions, please. There should not be

Re: [DISCUSS] requirements for commit messages and PRs

ional Description of Change" is better.  Perhaps "Affected Behaviors" is better than "Impact".  Testing is intentionally vagues. Greg On 6/4/2020 10:23 AM, Nathan Hartman wrote: On Thu, Jun 4, 2020 at 11:54 AM Gregory Nutt wrote: See https://github.com/nuttx

Reduced Participation

Effective immediately, I intend to reduce my particiapation in the Apache NuttX project.  I will stay on the PPMC and will vote and will an answer any questions.  I will express my opinion when needed (as in the case of that lousy PT template. But I will no longer be reviewing PRs, merging

Re: [DISCUSS] requirements for commit messages and PRs

. See https://github.com/nuttx-to-asf/incubator-nuttx/commit/b496ee7ff9adeaa9020e7b07efed8198d4e8e623 The is HORRIBLE!!!  God help us. Full disclosure:  I am the guy with the "lack of working project experience and vision"   who correct that original, horrible template.  I did

Re: [DISCUSS] requirements for commit messages and PRs

. See https://github.com/nuttx-to-asf/incubator-nuttx/commit/b496ee7ff9adeaa9020e7b07efed8198d4e8e623 The is HORRIBLE!!!  God help us.

Re: [OT] Linux now using 100 char lines as default

So sorry to be a radical humorist. I did not understand it was humor.  A smiley face would have helped.  Sorry. The chaos of this project is getting to me. Then, in that vein, why not just remove newlines altogether. ;) Each file can just be one long line.

Re: [OT] Linux now using 100 char lines as default

So sorry to be a radical humorist. I did not understand it was humor.  A smiley face would have helped.  Sorry. The chaos of this project is getting to me.

Re: [OT] Linux now using 100 char lines as default

-1 I like it the way it is.  And thoroughly opposed to increate the default line width.  There has been BS talk about it.  But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard.  There has been no change to

Re: [OT] Linux now using 100 char lines as default

-1 I like it the way it is.  And thoroughly opposed to increate the default line width.  There has been BS talk about it.  But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard.  There has been no change to

Re: [OT] Linux now using 100 char lines as default

-1 I like it the way it is.  And thoroughly opposed to increate the default line width.  There has been BS talk about it.  But it is just BS and amounts to nothing. No one should be taking this seriously. There has been no change to the coding standard.  There has been no change to default

Release 9.1

Hi, all If we are serious about getting on a two month release cycle again, now is the time to begin thinking about the 9.1 release. We created the 9.0 release branch sometime before the 15th of April.   We signed the release on April 23rd.  So we have some time, but also we need to start

[OT] HDMI for FPGAs

https://github.com/hdl-util/hdmi/ Discussed here: https://hackaday.com/2020/06/02/an-open-source-hdmi-implementation-for-fpgas/

Re: Duplicate task_spawn()

On 5/30/2020 1:27 AM, Yang Chung Fan wrote: Hi, Did anyone also noticed that when building with CONFIG_LIB_SYSCALL=y, the linker is unhappy about the duplicated task_spawn() symbols? One of them is in sched/ and other one is in libs/libc. PR 1168 should take care of this.

Re: bug report

I created PR 1167 to correct this per your description. On 5/31/2020 9:51 AM, 권석근 wrote: Hi, I found a bug at "pty.c" during ssh server implementation. When I turn on CONFIG_SERIAL_TERMIOS and OPOST|ONLCR on pty device for nsh console's stdin/stdout (ssh shell service), I've got system crash.

Re: MSYS2 build slow

FWIW the build has become noticeably faster for me with latest master: 1m21s now. Before, the build consistently took about 1m50s. So that's 30 seconds saved. I build on Linux. yes I have seen improvements of 25-30% on all platforms, and more on some Window's platforms that are more sensitive

Re: NuttX config browser

On 5/31/2020 6:12 AM, Maciej Wójcik wrote: Hello, On many occasions I want to lookup configuration options in NuttX and I found it inconvenient to run `menuconfig` for this. So I quickly created a small web interface and deployed it here http://nuttx-config.nxtlabs.pl It allows browsing

Re: MSYS2 build slow

There is no issue in reporting complaints here. :) The changes to Make.defs do also improve performance, however we need to do some hacks to get rid of the error messages. On Sun, May 31, 2020 at 1:16 PM Maciej Wójcik wrote: Thanks for explanation. I went through that PR right now. I was

Re: Duplicate task_spawn()

Any static should be conditioned on CONFIG_LIB_SYSCALL for the task_spawn() version in sched/task/task_spawn.c, however, that is not really necessary either because that version is not linked into the same binary as is the version in libs/libc/spawn. I suppose a user could enable

Re: Duplicate task_spawn()

On 5/30/2020 9:22 AM, Gregory Nutt wrote: On 5/30/2020 3:44 AM, Xiang Xiao wrote: It seems that the version inside sched/task/task_spawn.c need become a static function. I think that the version of task_spawn in lib/libc/spawn need to exist only if CONFIG_LIB_SYSCALL is selected

Re: Duplicate task_spawn()

On 5/30/2020 3:44 AM, Xiang Xiao wrote: It seems that the version inside sched/task/task_spawn.c need become a static function. I think that the version of task_spawn in lib/libc/spawn need to exist only if CONFIG_LIB_SYSCALL is selected.  In that case, the one in sched/task/task_spawn.c

Re: MSYS2 build slow

Without specifying -g CONFIG_HOST_LINUX is assumed. This worked well in the past with MSYS2. But I will try -g later today. Not if CONFIG_HOST_WINDOWS=y in the defconfig file.  That is what is set in stm32f4discovery:nsh: $ grep -r CONFIG_HOST

Re: MSYS2 build slow

For MSYS2 on my i7-3770 it's (every tests with jobs enabled): # make distclean # tools/configure.sh stm32f4discovery/nsh You really should specific -g on the configure.sh command line. Otherwise, the system will assume you are building for Cygwin. There are only a few differences between

Re: MSYS2 build slow

Johannes, PR 1149 has been merged.  That means that the incdir.c program has now been incorporated into the build system.  It all checks out:  I have pretty thoroughly verified it on Cygwin and Abdelatif and Alan Carvalho de Assis have checked it out well on Linux.  The PR also passes all of

Re: MSYS2 build slow

As a comparison I did:     - make clean     - make The dependencies only have to be recreated on the first build, not on subsequent builds.  In that case I get 3 minutes and 30 seconds.  So the Cygwin dependency generation vi mkwindeps.sh requires about 2 minutes by itself But with the

Re: MSYS2 build slow

I am most of the way through converting incdir.sh to a C version, incdir.c.  I will probably submit a PR that just adds the .c file (without changing the build system). Then we can experiment with it and make sure we are comfortable before bringing it into the build. I will first test with

Re: MSYS2 build slow

I must admit I thought about that idea also, but I wasn't sure about the portability issue. You could also think about a autogenerated Make.defs during configure with then hard coded include paths which should be the fastest possibility. Since Make.defs is already copied, perhaps it

Re: MSYS2 build slow

I must admit I thought about that idea also, but I wasn't sure about the portability issue. You could also think about a autogenerated Make.defs during configure with then hard coded include paths which should be the fastest possibility. Since Make.defs is already copied, perhaps it could

Re: MSYS2 build slow

Isn't there a possibility to cache the results of the system checks inside incdir.sh? The cost of getting 'os' is fork + new shell + uname The cost of gcc is fork + new shell + grep The cost of exfile if for + new shell + basename Yes, so that does have to fork a lot of additional shell

Re: MSYS2 build slow

By hardcoding os=Msys gcc=arm-none-eabi-gcc exefile=arm-none-eabi-gcc inside incdir.sh time tools/incdir.sh -s arm-none-eabi-gcc/home/Schock/nuttx/nuttx/include reduced from 180ms to 40ms. Overall, this reduced build time from 30min to an acceptable 6min. So incdir.sh is taking too much

Re: MSYS2 build slow

By hardcoding os=Msys gcc=arm-none-eabi-gcc exefile=arm-none-eabi-gcc inside incdir.sh time tools/incdir.sh -s arm-none-eabi-gcc/home/Schock/nuttx/nuttx/include reduced from 180ms to 40ms. Overall, this reduced build time from 30min to an acceptable 6min. So incdir.sh is taking too much

Re: MSYS2 build slow

By hardcoding os=Msys gcc=arm-none-eabi-gcc exefile=arm-none-eabi-gcc inside incdir.sh time tools/incdir.sh -s arm-none-eabi-gcc/home/Schock/nuttx/nuttx/include reduced from 180ms to 40ms. Overall, this reduced build time from 30min to an acceptable 6min. So incdir.sh is taking too much time

Re: MSYS2 build slow

Would please someone do the following command on Linux and Cygwin? time tools/incdir.sh -s arm-none-eabi-gcc /home/Schock/nuttx/nuttx/include (Replace the path with your NuttX path.) For MSYS2 it's in the range of: real0m0,189s user0m0,061s sys 0m0,045s I don't have the Linux

Re: api stability in apps/netutils/webclient

i want to add some stuff to apps/netutils/webclient. for example, * ability to report http status to the caller * ability to add some request headers * put * other content-type for post * tls a question: how much api stability is expected for this? Of course we would like the code to be

Re: The new Apache NuttX Logo

We should prefer SVG (or other widely-available and preferably open vector format) because that will allow the logo to be blown up to huge sizes or shrunk down to tiny sizes, without losing resolution or getting a blocky look. Yes! SVG is recommended by W3C and many image editors support it.

Re: The new Apache NuttX Logo

Before it's too late, I'd like to pose the question: Is there no-one who prefers NuttX be spelled with lower-case "utt"? That is the way the the registered trademark is spelled.. with lower case utt

Re: The new Apache NuttX Logo

Well, it could be a gift certificate of some kind.  Seems like it must be embedded RTOS themed in some way, however. Or maybe a trophy? Better... a T-shirt or hoody with the selected logo on it.

Re: MSYS2 build slow

it seems because ARCHINCLUDES try to figure out the search path by invoking shell script: But wouldn't that affect all platforms proportionally?  Why would that cause such a huge increase on MSYS2. I saw a 7 minute build time on Cygwin.  That is also very high, but not at all the kind

Re: MSYS2 build slow

it seems because ARCHINCLUDES try to figure out the search path by invoking shell script: But wouldn't that affect all platforms proportionally?  Why would that cause such a huge increase on MSYS2. I saw a 7 minute build time on Cygwin.  That is also very high, but not at all the kind of

Re: MSYS2 build slow

it seems because ARCHINCLUDES try to figure out the search path by invoking shell script: But wouldn't that affect all platforms proportionally?  Why would that cause such a huge increase on MSYS2. I saw a 7 minute build time on Cygwin.  That is also very high, but not at all the kind of

Re: The new Apache NuttX Logo

A contest is fine, maybe we could even create a pool to purchase a prize... like a nice, high end NuttX board? I would contribute. That would provide more incentive to participate. Let's find out if we can do this. Mentors? Is it allowed? Is there a process we have to follow? I wonder if

Kernel Threads with Custom Stacks

I tried to summarize the discussion of PR 1099 in a Wiki page. The PR comments got messy and unreadable, here is a cleaned up version: https://cwiki.apache.org/confluence/display/NUTTX/Kernel+Threads+with+Custom+Stacks

Re: The new Apache NuttX Logo

I want to ask a question based on the draft proposals. Are we allowed to think broader? :) For instance, I wonder what the community would think about using a mascot. I am open to that idea myself.. like Linux' penguin?  Such a mascot would need to have wide appeal and acceptance, I think a

Re: The new Apache NuttX Logo

On 5/27/2020 8:53 AM, Nathan Hartman wrote: On Wed, May 27, 2020 at 10:45 AM Gregory Nutt wrote: The new logo could be viewed online here: https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo Please give your feedback and suggestoion. Are there any updates on the proposed

Re: The new Apache NuttX Logo

The new logo could be viewed online here: https://cwiki.apache.org/confluence/display/NUTTX/New+Apache+Nuttx+Logo Please give your feedback and suggestoion. Are there any updates on the proposed new NuttX logos?  We stopped discussing this with no follow through plan. I suppose that with

Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set

I'm currently updating MSYS2, and will then repeat the build. Then I'll test on another computer. And when it's happening there as well, I'll try to narrow down the reason. I just configured a new computer and I am having problems with MSYS2.  I can't even create the "symbolic" links

Re: kconfig (Re: mbedtls)

I agree, and all the more reason we should ensure that our project has a controlled snapshot of this tool -- and to ensure the longevity of that snapshot so that it will not be lost suddenly! There is also a snapshot of genromfs in the tools repository. This is a snapshot of the tool from

Re: kconfig (Re: mbedtls)

On Mon, May 25, 2020 at 11:48 AM Gregory Nutt wrote: A snapshot was taken and has never disappeared from internet contrary to other statements it is always been here and will always be here: https://bitbucket.org/nuttx/tools/src/master/ Correct. I meant that the original (from Yann Morin

Re: kconfig (Re: mbedtls)

On 5/25/2020 10:03 AM, Nathan Hartman wrote: On Mon, May 25, 2020 at 11:48 AM Gregory Nutt wrote: A snapshot was taken and has never disappeared from internet contrary to other statements it is always been here and will always be here: https://bitbucket.org/nuttx/tools/src/master/ Correct. I

Re: kconfig (Re: mbedtls)

We should all be using a consistent, common version of kconfig-frontends.  A snapshot was taken and has never disappeared from internet contrary to other statements it is always been here and will always be here: https://bitbucket.org/nuttx/tools/src/master/ Since the kconfig-frontends

Re: kconfig (Re: mbedtls)

We should all be using a consistent, common version of kconfig-frontends.  A snapshot was taken and has never disappeared from internet contrary to other statements it is always been here and will always be here: https://bitbucket.org/nuttx/tools/src/master/ We do not accept any  Python-based

Re: mbedtls

Yes, we can reuse github.com/nuttx to host the 3rd party library which stop the active development. But It's better to host the library by the different git to keep the full history for each project. I think it could be used in projects in active development too. I have seen people take a

Re: mbedtls

Yes, I think it could live at github.com/nuttx/apps-externals I'm not a big fun of git submodules but it could be a way to integrate the a copy of external projects that could live as forks there. Please ... no submodules in the git repositories!  The don't work for people who don't use

Re: Get size of block character device file with stat()

It looks like I overthink and the best and simple solution is just to use for all block devices the block_operation function of inode to get geometry: inode->u.i_bops->geometry I miss that bchlib is already use this function to fill bchlib_s structure. Will try this approach now. The bch

Re: Don't need use $(DELIM) in include statement

I think we should continue to wait a while and continue doing community building. Meanwhile, one of the following might happen: * Either someone joins and fixes/maintains the Windows build, or * Windows support for *nix compatibility will become much more extensive over time I have a feeling

Re: Don't need use $(DELIM) in include statement

I'm confused about commit edb0ce2d5afa8a0905bd4536ac39eaf1819dfc56: "build: Don't need use $(DELIM) in include statement" This changes various lines in Make.defs from this: include wireless$(DELIM)spirit$(DELIM)drivers$(DELIM)Make.defs to this: include

Re: Don't need use $(DELIM) in include statement

I'm confused about commit edb0ce2d5afa8a0905bd4536ac39eaf1819dfc56: "build: Don't need use $(DELIM) in include statement" This changes various lines in Make.defs from this: include wireless$(DELIM)spirit$(DELIM)drivers$(DELIM)Make.defs to this: include wireless/spirit/lib/Make.defs

Re: mbedtls

I’m concerned that you are discussion doing work outside of the Apache repositories. Why is the main issue here? I think Alan summarized this well.  We are already doing work outside of the Apache repositories here: https://bitbucket.org/nuttx/?repo_name=apps-old .  We have discussed

Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set

PR #1105 should eliminate the primary cause of the error: fs_fdopen() will not longer set the errno  variable.  The secondary error, the uninitialized stack description, is still a problem. Since the errno value was only set before fs_fdopen() failed, this means that you system will still

Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set

PR #1105 should eliminate the primary cause of the error: fs_fdopen() will not longer set the errno  variable.  The secondary error, the uninitialized stack description, is still a problem. On 5/22/2020 10:19 PM, Gregory Nutt wrote: The new implementation of set_errno require all thread

Re: Arm Kinetis: set_errno in nx_start with CONFIG_TLS_ALIGNED not set

The new implementation of set_errno require all thread(include IDLE) initialize the stack related fields in tcb_s correctly. But many chipset forget to setup them for IDLE thread. TODO contain an item described this: ... snip ... Hello, I think there's a problem with set_errno() in

Re: Release Notes for the NEXT version of NuttX

This is what I used to do for the old releases (from 8.2 tools/README.txt, from show 6168f3ebf046e4c3d5561bfa96a39d0f02b771db): index 42c71fd52d..64666eb550 100644 --- a/tools/README.txt +++ b/tools/README.txt @@ -745,15 +745,6 @@ link.sh, link.bat, copydir.sh, copydir.bat, unlink.sh, and

Re: mbedtls

I propose that we reuse the same process(Apache Way) for github.com/nuttx(e.g. review/merge, select new committer/PMC). The only difference is that github.com/nuttx isn't an Apache project and is an optional component. I think other than the repository location, it can piggyback completely

Re: mbedtls

i guess a user often want to use apache-nuttx-external AND his own version. while you can always workaround it with symbolic links, i wonder if it could be more straightforward to use multiple "external" repos. People have talked about this on and off for some time in various way.  There

Re: Automated Testing

I am wondering it's possible to test on the real hardware if we don't get the donation from the commercial company. Another option is to make the test software design so that it does not depend on any particular hardware.  I would like to be able to run the tests on my desks using hardware

Re: nxstyle warnings: Fail precheck?

What to do about lines of code like this: ... # define GPIO_CNF_INPULLDWN (2 << GPIO_CNF_SHIFT) /* Input pull-down */ # define GPIO_CNF_INPULLUP ((2 << GPIO_CNF_SHIFT) | GPIO_OUTPUT_SET) /* Input pull-up */ ... I would probably fix that like: # define

Re: nxstyle warnings: Fail precheck?

I created PR https://github.com/apache/incubator-nuttx/pull/1079 to eliminate any distinction between C source file and header files in reporting long lines.  Both are equally errors.

<    4   5   6   7   8   9   10   11   12   13   >