There is way to much speculation here (and some jus wrong statements).
Someone just needs to open an Apache JIRA ticket with legal and you will
get an offical answer.
--Brennan
On Thu, Oct 19, 2023, 2:54 AM Andrew Dennison
wrote:
> Hi all,
>
> Wow, i didn't think we were doing anything othe
I'm very confused as to the issue here. This is not GPL code, this is code
that is dual licensed. I think two totally different topics are being
conflated here.
I have code that was part of the dual licensing of the CAN code being
discussed here (outside of NuttX) and the whole point of dual licen
On Thu, Sep 7, 2023, 9:01 AM Gregory Nutt wrote:
>
> > I think GPL code shouldn't be included directly, but I think it is
> > fair to allow GPL code be downloaded using the building system case
> > user selected it.
>
> We created this directory specifically to hold forks of GPL code that
> can b
I would not recommend doing that. You _could_ but it will break for non
flat builds and you are explicitly violating the the OS application
interface boundary. You may also break assumptions of the OS and make it
unstable by changing important registers in interrupt controller.
So nothing is stopp
On Tue, Aug 8, 2023, 5:22 PM Andrew Dennison
wrote:
> Hi Nuttx Dev,
>
> We are negotiating with the authors of the linux device driver for the CTU
> CAN FD IP core to it re-licenced from GPL to so the driver can then be
> ported to Nuttx.
>
> I've seen various licencing examples in the nuttx code
On Sun, Aug 6, 2023, 5:47 PM Nathan Hartman
wrote:
> On Sun, Aug 6, 2023 at 6:02 PM Brennan Ashton
> wrote:
>
> > On Sun, Aug 6, 2023, 2:41 PM Milan Obuch wrote:
> >
> > > On Mon, 31 Jul 2023 10:51:33 -0300
> > > "Alan C. Assis" wrote:
>
On Sun, Aug 6, 2023, 2:41 PM Milan Obuch wrote:
> On Mon, 31 Jul 2023 10:51:33 -0300
> "Alan C. Assis" wrote:
>
> > Hi Milan and Tomek,
> >
> > It should be nice to have our CI testing on FreeBSD as well.
> >
> > Milan, after you get the port done, please let us know if you can help
> > us to ge
Email aggressively remove the sender from the reply list when sent to a
list so they likely did not get this email. I was doing the same thing a
couple weeks ago Added them to this one.
Sharwin Patil hopefully you get this response from Nathan.
--Brennan
On Thu, Jun 8, 2023, 6:28 PM Nathan H
On Mon, May 29, 2023 at 2:41 AM Michael Gielda wrote:
>
> Haha, no worries, just subscribed on Friday for this particular reason :)
> glad Renode was useful for EOS S3 and of course happy to see how we can
> enable more of that.
>
>
> You mention you have a CI generating all the elfs, could you
Still dropped him. Apparently I cannot use email correctly today...
On Fri, May 26, 2023, 3:40 PM Brennan Ashton
wrote:
> Adding Michael back since I responded to him and he might not be on the
> list...
>
> On Fri, May 26, 2023 at 3:23 PM Brennan Ashton
> wrote:
> >
>
Adding Michael back since I responded to him and he might not be on the list...
On Fri, May 26, 2023 at 3:23 PM Brennan Ashton
wrote:
>
>
>
> On Fri, May 26, 2023, 3:11 PM Michael Gielda wrote:
>>
>> Hi Alan, nice to meet you Nathan,
>>
>> Indeed, we discuss
On Fri, May 26, 2023 at 3:11 PM Michael Gielda wrote:
>
> Hi Alan, nice to meet you Nathan,
>
> Indeed, we discussed with Alan some time ago, having a Nuttx-focused
> dashboard can be done and we assume would be useful. We just didn’t get to
> that as it would have been yet another research projec
On Fri, May 26, 2023, 3:11 PM Michael Gielda wrote:
> Hi Alan, nice to meet you Nathan,
>
> Indeed, we discussed with Alan some time ago, having a Nuttx-focused
> dashboard can be done and we assume would be useful. We just didn’t get to
> that as it would have been yet another research project (
On Tue, May 23, 2023, 5:05 AM Nathan Hartman
wrote:
> On Tue, May 23, 2023 at 6:12 AM Brennan Ashton
> wrote:
> > I have also asked in the past about cutting down on the amount of configs
> > we have checked in to be something like
> >
> > board:nsh
On Mon, May 22, 2023, 12:14 PM Nathan Hartman
wrote:
> On Mon, May 22, 2023 at 9:29 AM Sebastien Lorquet
> wrote:
>
> >
> > If the untold reason is to speed up github tests, then run less tests.
> > Do we really need to test build on 13 or 20 arm platforms when only one
> > config of the other a
On Sun, May 21, 2023, 8:02 AM Gregory Nutt wrote:
> On 5/21/2023 8:12 AM, Nathan Hartman wrote:
> > Recently I added the new docs [1] and [2] to Documentation/guides but
> > they are not appearing on the website [3].
> >
> > Does anyone know what I missed?
> >
> > [1]
> https://github.com/apache/
On Fri, May 19, 2023, 3:23 PM Tomek CEDRO wrote:
> I am thinking about this. "If it works don't fix it" comes to my mind.
>
> Current build system is amazingly simple coherent and fast. Building
> firmware takes 17 seconds. Why change it?
>
> Such change will flip everything upside down. Adds lot
On Thu, May 18, 2023, 11:53 AM Alan C. Assis wrote:
> I don't think you can get ws2812 working directly using a GPIO over
> bitbang, the protocol used by this chip is very time sensitive.
> Actually even in SPI mode I failed to get it working, I tried it on
> stm32f103-minimum and stm32f4discover
On Wed, May 17, 2023, 5:13 AM Nathan Hartman
wrote:
>
> Let's create a blog section on the nuttx.apache.org site and fill it with
> articles like these!
>
> Cheers
> Nathan
>
This is supported, just no content added
See https://github.com/apache/nuttx-website/tree/master/_posts
>
>
> The first author that comes to mind, just off the top of my head, is Derek
> Molloy, the author of books like Exploring Raspberry Pi [1] and Exploring
> BeagleBone [2]. Both of these are about embedded systems. Both of these
> include tutorials not only in electronics (how to use FET transistor
On Tue, Apr 25, 2023 at 8:46 AM Brennan Ashton
wrote:
>
>
>
> On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
>>
>>
>> > Thanks Alan! This is why I was a bit surprised why the documentation
>> > is not direct part of the source code (i.e. documentation
On Sun, May 14, 2023, 1:12 PM Tomek CEDRO wrote:
> One last question: how is the website updated? :-P
>
> By running publish.sh ?
>
> Is it safe to run?
>
This is handled by CI. I just put up a PR to fix the publish issue
triggered by your git user.name. Once that merges this will publish.
--br
On Wed, May 10, 2023, 6:34 PM Tomek CEDRO wrote:
> Silly question.. why some places use release name 12.1.0 (i.e. running
> firmware) and some other places use 12.1?
>
> Shouldn't we stick to one coherent versioning convention? 12.1.0?
Since becoming an Apache project all releases have used the
On Tue, Apr 25, 2023, 7:45 PM Tomek CEDRO wrote:
> On Tue, Apr 25, 2023 at 8:14 PM Gregory Nutt wrote:
> > Tomasz Cedro now owns nuttx.com and nuttx.org.
>
> Yes the domains are for the project use, just let me know how you want
> them configured, at this point they redirect to the main project s
On Tue, Apr 25, 2023, 7:14 PM Gregory Nutt wrote:
> On 4/25/2023 11:38 AM, Nathan Hartman wrote:
>
> > I like the idea of keeping documentation in sync with the code(as much
> as
> > possible given our volunteer-based project).
>
> I wouldn't make a plan that depends on that. Engineers are not
On Tue, Apr 25, 2023, 6:10 PM Tomek CEDRO wrote:
> On Tue, Apr 25, 2023 at 5:47 PM Brennan Ashton wrote:
> > On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
> > > My experience with using Deoxygen on large, projects has been
> > > disastrous. People don't
Linux only is verified?
>
> вт, 25 квіт. 2023 р. о 19:45 Brennan Ashton
> пише:
>
> > On Tue, Apr 25, 2023, 5:41 PM Brennan Ashton
> > wrote:
> >
> > >
> > > On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
> > > petro.karashche...@gmail.c
On Tue, Apr 25, 2023, 5:41 PM Brennan Ashton
wrote:
>
> On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
> petro.karashche...@gmail.com> wrote:
>
>> Hello,
>>
>> I'm starting to experiment with NuttX BLE support. I have a device that I
>> can succ
On Tue, Apr 25, 2023, 5:36 PM Petro Karashchenko <
petro.karashche...@gmail.com> wrote:
> Hello,
>
> I'm starting to experiment with NuttX BLE support. I have a device that I
> can successfully pair with my phone and I would like to try pairing it with
> the NuttX based device. I chose ESP32 for m
On Tue, Apr 25, 2023, 3:18 PM Gregory Nutt wrote:
>
> > Thanks Alan! This is why I was a bit surprised why the documentation
> > is not direct part of the source code (i.e. documentation of the
> > file/module/function right in that file/module/function). Kivy does
> > that, it helps understandin
On Tue, Apr 25, 2023, 1:46 PM Brennan Ashton
wrote:
>
>
> On Tue, Apr 25, 2023, 1:37 PM Tomek CEDRO wrote:
>
>> Hello world :-)
>>
>> I was on a trip recently (and it happens quite often) so I was looking
>> for a PDF version of NuttX Documentation, kind of
On Tue, Apr 25, 2023, 1:37 PM Tomek CEDRO wrote:
> Hello world :-)
>
> I was on a trip recently (and it happens quite often) so I was looking
> for a PDF version of NuttX Documentation, kind of Handbook, but I did
> not find one.
>
> I got used to PDF Handbook style because it is all-in-one appro
On Tue, Apr 25, 2023, 6:10 AM Gregory Nutt wrote:
>
> On 4/24/2023 7:27 PM, Andrew Dennison wrote:
> > Are there any examples of a gdb setup to debug a userspace process? One
> key
> > issue is to setup the section offsets to match the final application
> > location once it has been loaded.
>
Th
On Sun, Apr 23, 2023, 3:57 PM Gregory Nutt wrote:
>
> > Possibly stupid idea: Maybe OStest needs
> That point is that there was a lot of valuable documentation that has
> been thrown in the shitcan and replaced with superficial how-to
> documentation. There is no longer technical documentation i
t up some kind of online pot that people can
> put
> > some money into without too much hassle?
> >
> > On Fri, Mar 10, 2023 at 1:27 PM Alan C. Assis wrote:
> >
> >> Hi Brennan,
> >>
> >> I think it should be nice if you can receive it.
> >>
If this is something people really do want. I'm happy to hold them in the
US and help lend out and cover this shipping to get it from Costa Rica.
Sounds like from a customs and tax standpoint that might be easier?
--Brennan.
On Fri, Mar 10, 2023, 10:02 AM Gregory Nutt wrote:
> Earlier someone s
This is the sheet (a little old now) that I had shared out:
https://docs.google.com/spreadsheets/d/1qMQV_CSN5Ka13_wr73QNo2Uh-NiSumjcwINuc0BkyIs
My goal had been to functional test as much as I could for that release,
and I did find a bunch of little things to fix that I think made for a
better re
I do have a lot of changes in a local branch, but have not had much time to
focus on this. The early stage bring up is not well documented and fairly
challenging. You can find my notes here as well.
https://btashton.github.io/bl808-notes/
If you would like to collaborate on this that would be aw
This whole thread really bums me out. We really should be assuming people
are acting with best intentions, rather than accusing of ulterior motives.
If there are changes that you have concerns about people tend to be very
reasonable about explaining and if we need to revert something or change
some
els
> that of the sources?
>
Yes.
> One thing I think needs to always remain true is that the docs should
> always be in the nuttx repo and *not* move to a separate repo or other kind
> of CMS.
>
> Cheers
> Nathan
>
> On Wed, Jan 18, 2023 at 10:08 PM Brennan Ashton >
I would like to just move to the documentation section. There is way too
much duplicate out of date common information in the existing readme. The
new documentation has the ability to actually link things.
Also CI is smart and will only build documentation and not all of the
builds if you make ch
On Mon, Jan 2, 2023, 4:46 AM Alan C. Assis wrote:
> Thank you very much Brennan,
>
> I was afraid to change the hash because I wasn't sure that the file
> wasn't corrupted/infected.
>
> How did you check it was a legit hash change?
>
In the PR I linked to the relevant upstream issue. It was not
Please see this PR for a fix and the root cause.
https://github.com/apache/nuttx/pull/8018
On Fri, Dec 30, 2022 at 11:53 AM Alan C. Assis wrote:
>
> Thank you very much Brennan!
>
> BR,
>
> Alan
>
> On 12/30/22, Brennan Ashton wrote:
> > Alan, I mentioned th
Alan, I mentioned this earlier in another issue. I believe I know what the
issue is and am fixing it this week. There are a couple things that need
to be fixed. Juts give me a little bit as it is the holidays.
--Brennan
On Fri, Dec 30, 2022, 10:58 AM Alan C. Assis wrote:
> Dear busy NuttXers,
I'll update the files linked on that page in SVN this evening to reflect
the updated status.
--Brennan
On Mon, Dec 26, 2022, 10:05 AM Nathan Hartman
wrote:
> On Mon, Dec 26, 2022 at 9:44 AM Calvin Kirs wrote:
>
> > On Mon, Dec 26, 2022 at 10:36 PM Nathan Hartman
> > wrote:
> > >
> > > On Sun,
This should be resolved now with these two PRs that have merged.
https://github.com/apache/incubator-nuttx/pull/7632
https://github.com/apache/incubator-nuttx-apps/pull/1435
--Brennan
On Sat, Nov 19, 2022, 12:45 PM Brennan Ashton
wrote:
> It has to do with the CI configuration, but sho
It has to do with the CI configuration, but should not be breaking
anything. I'll put up a PR today to bump the version we use. The build
itself should be running in a 22.04 container already.
Thanks for the reminder!
--Brennan
On Sat, Nov 19, 2022, 12:17 PM Tim Hardisty wrote:
> The checks o
My vote without too much care is to leave it be minus the incubation bit.
We have already been dealing with the hyphens.
--Brennan
On Thu, Nov 17, 2022, 1:47 PM Nathan Hartman
wrote:
> Hi all,
>
> As mentioned in the other thread, the repos need to be renamed to
> remove "incubating".
>
> In th
I can probably help revive my past effort to run some native builds in CI
to at least prevent it from getting fully broken. One of the blockers last
time, was just how slow it was and the limited number of Windows workers.
Let's see what we can do.
--Brennan
On Sat, Nov 12, 2022, 5:43 AM fft wr
+1 for graduation!
On Fri, Oct 21, 2022, 5:47 AM Nathan Hartman
wrote:
> Dear Apache NuttX Community,
>
> Following the [DISCUSS] thread which has gone 72 hours without any
> further issues raised [1]:
>
> This is a call to VOTE on Graduation of Apache NuttX from the
> Incubator to Top-Level Pro
Some of these are are people's names or in documentation, I don't see any
reason to update that. Things like mu or I2C seems reasonable to convert
for searchability.
--Brennan
On Mon, Oct 10, 2022, 8:33 AM Fotis Panagiotopoulos
wrote:
> Shall I enhance nxstyle to check for this? Is this the c
Nice work! You suckered me into getting one of these to follow along :)
--Brennan
On Wed, Aug 31, 2022, 6:48 PM Lee, Lup Yuen wrote:
> NuttX on Pine64's PinePhone had some issues with Arm64 Interrupts. This
> article explains how I fixed them, also how I ported NuttX's GIC v2 from
> Arm32 to Ar
Pulling in that SDK upstream is likely not feasible for multiple reasons
including the licencing side. That said there already is some support for
the BCM43xxx chips which if I recall correctly are the same family, and it
may be not too much work to add missing support.
--Brennan
On Sat, Jul 9, 2
I had tried to just handle the difference via config flags but it got too
complicated (different pin mappings, inverted signals, clocking, etc...).
The original board is quite different and is closer to the F series boards
than the H ones.
On Wed, Jun 29, 2022, 6:53 AM Alan Carvalho de Assis
wrot
+1
Thanks Alin!
On Fri, Jun 10, 2022, 1:33 AM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> +1 to release.
> The only issue we had with the previous RC was the disclaimer, and now
> it's there!
>
> On Wed, Jun 8, 2022 at 8:17 AM Alin Jerpelea wrote:
> >
> > Hello all,
> > Ap
On Mon, Feb 14, 2022, 9:28 AM David Sidrane wrote:
> I am opening this discussion to widen the audience for feedback on the
> rules for merging. The original interexchange was in [1]
>
>
>
> 1 ) Given the geographical and time differences should we consider that
> once a review with approval* has
I really think we need to address the existing feedback from the last two
releases before we go asking for more.
We also need to go through the process of a release without the WIP
disclaimer which should also solicit some of the remaining feedback.
--Brennan
On Mon, Feb 14, 2022, 9:00 AM Nathan
This is taken care of by infra.
Major outstanding bits are around the export control stuff which is mostly
just paperwork and there apache org has good documentation for.
There is also some code still in the repo with restrictions on use to a
single microcontroller. That have come up in votes bef
cute "install_tools" function
>
> -- Original --
> From: "Brennan Ashton" Date: Wed, Feb 2, 2022 04:17 PM
> To: "dev"
> Subject: Re: enable the excute of install_tools in cibuild.sh
>
>
>
> The ci uses the docker containe
The ci uses the docker container. You will want to submit a PR updating
that and have that merge first.
https://github.com/apache/incubator-nuttx/blob/master/tools/ci/docker/linux/Dockerfile
On Tue, Feb 1, 2022, 11:37 PM fft wrote:
> Hi team's
> I'm try to add sparc to the daily ci,I add code
Yep this is something I have looked into before as well and a ticket with
some discussion I had opened.
https://github.com/apache/incubator-nuttx/issues/2028
It's something I will probably revisit sometime, but not something I am
actively working on.
--Brennan
On Fri, Jan 14, 2022, 4:02 PM Greg
Yeah,
Microchip never upstreamer the 32bit work and if you look at the source
parts of it are very ugly and based on a quite old version of gcc. They do
still host the source but it is behind a login wall.
https://www.microchip.com/en-us/development-tools-tools-and-software/gcc-compilers-avr-and-a
The nxflat stuff in that repository is broken for modern gcc. I fixed it
and have hosted it standalone here as well as added some basic CI.
https://github.com/btashton/nxflat
--Brennan
On Sun, Oct 17, 2021, 7:38 AM Nathan Hartman
wrote:
> On Sun, Oct 17, 2021 at 9:10 AM Abdelatif Guettouche
>
> >Remove no PPMC/Commiter from admin group
> >
> > Either way is fine, but we need action now. I have seen the same topic
> > happen on the email list many times, but nothing happens after that
> > discussion.
> >
> > On Sun, Oct 17, 2021 at 1:26 AM Brenn
Agreed it will just complicate things moving towards graduation. I had
asked for it to be taken down a long time ago.
--Brennan
On Sat, Oct 16, 2021, 7:10 AM Gregory Nutt wrote:
> No, https://github.com/NuttX/nuttx is just garbage and should be deleted.
> It has nothing to do with Apache NuttX
apache.org/docs/10.0.0/quickstart/index.html#
>
> And as per these two links I have followed, successfully created
> *nuttx.bin* and *nuttx.hex* files in nuttx directory.
>
> Still neither minicom is working nor picocom.
>
> Please help me with this.
>
>
>
> Thanks &a
artifacts as well.
https://asciinema.org/a/429943
--Brennan
On Tue, Aug 10, 2021 at 8:16 PM Brennan Ashton
wrote:
>
> This board is part of my 30 or so boards I test for releases. I suspect there
> is something else up although later tonight I could give it a go. I usually
>
This board is part of my 30 or so boards I test for releases. I suspect
there is something else up although later tonight I could give it a go. I
usually test via the artifacts that are attached to the CI build job so it
is faster to check and also makes sure there is nothing special about my
conf
On Mon, Jul 19, 2021, 3:05 PM Nathan Hartman
wrote:
> It seems that quite a few docs are in the CWIKI and not in the repo.
> For example, recently I looked for the article about High Performance
> / Zero Latency Interrupts [1] and unless I missed something, it's not
> in Documentation in the repo
/execution.
This issue is also known as BadAlloc
Credit:
Apache NuttX would like to thank Omri Ben-Bassat of Section 52 at Azure
Defender for IoT of Microsoft Corp for bringing this issue to our
attention.
--Brennan Ashton
On Wed, Jun 9, 2021, 11:04 AM Fotis Panagiotopoulos
wrote:
> For me, cmake would be a no.
> The reasons are greatly outlined by Sebastien.
>
> However, I am not very experienced with it. (I just never liked it...)
> Are there any hard advantages that would justify such a migration?
>
> Are there
>
> We already do so much to try and not break things. If you are going to
> jump 3 major release versions that span __6 years__ you have to expect to
> run into something and should read at least the compatibility comments for
> the major releases.
>
Should have said 2 years not 6 (7.3 was 6). Bu
On Fri, May 28, 2021, 7:54 AM Nathan Hartman
wrote:
> On Fri, May 28, 2021 at 9:12 AM Sebastien Lorquet
> wrote:
>
> > I'm not talking of renaming code symbols like up_anything to
> > arm_anything, which makes sense and can be noticed quite easily at link
> > stage.
> >
> > I'm talking about ren
On Mon, May 24, 2021, 2:09 PM Nathan Hartman
wrote:
> I noticed this message [1] from Jarek Potiuk to builds@a.o about a new
> concurrency feature of GitHub Actions. Interesting to us?
>
> [1]
> https://mail-archives.apache.org/mod_mbox/www-builds/202105.mbox/%3cCAH067R=0A0oQhn2SghOKmdj561KvXGKjM
On Sun, May 23, 2021, 6:32 AM Miguel Wisintainer
wrote:
> Sir
>
> How are you ?
>
> I compiled the SDC Nimble to run on NRF52832 but i am getting the
> following error
>
> NuttShell (NSH) NuttX-10.1.0-RC1
> nsh> ERROR: nrf52_sdc_initialize() failed: -45
>
You will likely need to turn on the wire
#x27;m hoping that with CMake we can really improve our build time (that is
> the impression
> I get locally as well).
>
> Best,
> Matias
>
> On Tue, May 18, 2021, at 15:10, Brennan Ashton wrote:
> > I saw this a few days ago when GitHub was having some issues and it lo
I saw this a few days ago when GitHub was having some issues and it looks
like they have an active outage now as well that is recovering so I would
suspect that.
https://www.githubstatus.com/
--Brennan
On Tue, May 18, 2021, 10:17 AM Matias N. wrote:
> I noticed CI wasn't running jobs and found
NuttX
> >>> project "NuttX Support for RapidControl Applications Development with
> >>> pysimCoder" a the GSOC!
> >>>
> >>> I'm very excited to share with you my experience during this project,
> >>> and I hope that your contribution can help in develop and sharing
> >>> pysimCoder with the community.
> >>>
> >>> I think that we can organize ASAP a video meeting, perhaps with Prof.
> >>> Pisa and Brennan Ashton.
> >>>
> >>> Best regards
> >>>
> >>> Prof. Roberto Bucher
>
>
>
>
Hey everyone,
We had multiple students this year propose projects for the NuttX project
under Apache to Google Summer of Code (GSOC), and I'm excited to share one
of them was accepted.
Michal Lenc will be working on his project titled: NuttX Support for Rapid
Control Applications Development with
For what it's worth, there are a bunch of people here that use macOS
(including our CI testing) and I have used both Cygwin and WSL. So if there
is a problem with any of these it is very important that we work with you
to resolve it rather than drive you to another OS where you may run into
the exa
+1 :
- LICENSE, NOTICE and DISCLAIMER files exit in both repos.
- Signatures and checksums valid.
- Can build from source.
Tested this specific release on:
Bl602
Nucleo-h743
Nucleo-h745
Nucleo-f413
Nucleo-f767
Launchpad TM4C123GXL
EOS S3 QuickFeather
--Brennan
On Thu, May 6, 2021, 1:41
On Thu, Apr 29, 2021, 10:46 PM yuta wrote:
>
> I changed "System timer tick period (microseconds)" from 1 to 1000
> then I got 1.001000 sec in result which is more exact than before.
> I'll try Tickless OS configuration if I need later.
>
Increasing the tick rate may increase the resolution
On Thu, Apr 29, 2021, 10:07 AM yuta wrote:
> Brennan,
> Thank you for your advice.
>
> I checked links you shared and
> https://www.gnu.org/software/libc/manual/html_node/CPU-Time.html
> I got elapsed time. Thank you.
>
> However I'm wondering why the elapsed time I got was not exactly the same
>
On Thu, Apr 29, 2021, 8:16 AM yuta wrote:
> Hi all.
>
> I'm new to NuttX.
>
> I'm not sure if it's no problem me asking some personal question about
> NuttX here. (please tell me if better place to ask.)
>
> by the way, I have made my app in apps/examples/. It's working
> well. Now, I would like
Max,
Sorry you are having trouble, I agree mailing lists are hard to use without
subscribing and I think you found what would have been my suggestions for
accessing the archives. I included you directly in this response so
hopefully you will get it.
If you have "issues" that you want to discuss su
Just as a heads up Github has implemented a change to help combat spam
accounts using our CI resources for crypto mining and the like. I
don't know of any cases of this happening to this project, but many
other projects have been hit with this.
Going forward the first time someone submits a PR a
Alin,
I think we should consider if we want to backport these into the
10.1.0 release. I am still running more tests myself on all the
hardware I have, but these seemed important to at least consider.
https://github.com/apache/incubator-nuttx/pull/3586
https://github.com/apache/incubator-nuttx/pul
On Wed, Apr 21, 2021 at 5:59 PM Masayuki Ishikawa
wrote:
>
> Hi, Brennan
>
> Sorry to reply to the old email but I noticed that the following tags are
> missing in the github repositories.
>
> https://github.com/apache/incubator-nuttx/
> nuttx-9.1.1
>
> https://github.com/apache/incubator-nuttx-a
/dist/dev/incubator/nuttx/10.1.0-RC0/
gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created
gpg: key E1B6E30DB05D6280: public key "
Alin,
These are still a draft and I will send them as a PR to our
documentation, but here are my notes for cutting the release.
https://gist.github.com/btashton/ee474723013a7040186c91d41a4c7fad
--Brennan
On Sat, Apr 17, 2021 at 11:14 AM Brennan Ashton
wrote:
>
> Alin,
> Apologie
> On 2020/12/13 22:19:01, Brennan Ashton wrote:
> > Yeah 100% agree which is why I need to look when I have a little more>
> > time to understand what is going on.>
> >
> > On Sun, Dec 13, 2020 at 2:12 PM Gregory Nutt wrote:>
> > >>
> &
Alin,
Apologies for not getting to it this week I will write something today with
the exact details, but here is a quick summary:
First we need to submit a PR with the updated release notes to master and
then also a backport of that to the release branch. Once all of that is
done you need to push
On Mon, Apr 12, 2021, 9:01 PM Tanushree Baindur
wrote:
> Thanks a lot for your reply. I used menuconfig to generate the .config file
> this time and noticed the elf relocation error for 64 bit. So I enabled the
> option "Build 32-bit simulation on 64-bit machine" under System Type to
> set CONF
Tanushree,
Couple notes to get you going here. First off you really want to
avoid editing the .config file directly and instead use menuconfig so
that the dependencies are handled correctly. You can use "/" to
search for config settings.
I tweaked the nsh config like this and was able to make it
On Sun, Apr 11, 2021 at 9:19 PM Nathan Hartman wrote:
>
> On Mon, Apr 12, 2021 at 12:10 AM Brennan Ashton
> wrote:
>
> > I generated the project board for all the OS PRs in this release
> > cycle. I already sorted out a bunch of minor ones, but there are
> > ar
x/tree/releases/10.1
>
> I propose that we test this branch and backport all fixes until 16 April then
> we cut RC0
>
> Regards
> Alin
>
>
>
> -Original Message-
> From: Brennan Ashton
> Sent: den 5 april 2021 03:50
> To: dev@nuttx.apache.org
> S
Erick and Alan I would be happy to help mentor this. This has been
something I have been considered taking on myself off and on for the last
year or so.
--Brennan
On Tue, Apr 6, 2021, 8:22 AM Alan Carvalho de Assis
wrote:
> Hi Erick,
>
> Thank you! We are looking forward to get Rust support on
On Thu, Apr 1, 2021 at 1:40 PM Abdelatif Guettouche
wrote:
>
> Hi Alin,
>
> There are a few notes here [1] including the pre-Apache release checklist.
> However, for the "pre-release" process, what has been done for earlier
> releases is the following:
> 1. Agree on a date to create the release br
Part of the issue here is also limits across the organization. This has
been discussed for a couple months now on the Apache build mailing lists
and the GitHub has been part of them trying to figure out a smart path
forward.
We were sharing cache but ran into some strange issues with collisions an
On Thu, Mar 25, 2021 at 11:21 AM Alan Carvalho de Assis
wrote:
> >>
> >> > Regarding SSL, is it required to build? Maybe it can be initially
> >> > integrated without
> >> SSL support?
> >>
> >> You can use it with no SSL support. But MQTT-C supports multiple
> >> crypto libraries, mbedTLS being
1 - 100 of 420 matches
Mail list logo
