There have been numerous fixes for Cortex-A SMP since 7.31. You might
want to upgrade.
On 7/29/2020 10:19 AM, Mansfield, Ryan wrote:
Hi,
We are trying to enable SMP for a dual core ARM Cortex-R8. We are using a
kernel based on NuttX-7.31, with added proprietary support for our embedded
Cort
On Wed, Jun 3, 2020 at 4:23 AM Alan Carvalho de Assis wrote:
>
> Hi Takashi,
>
> Do you think it could be possible to create a HTTP REST framework for
> NuttX similar to Ulfius:
>
> https://babelouest.github.io/ulfius/
>
> https://www.hackster.io/babelouest/http-rest-framework-in-c-for-embedded-sy
On Fri, May 29, 2020 at 3:23 PM Takashi Yamamoto wrote:
>
> hi,
>
> On Fri, May 29, 2020 at 7:00 AM Gregory Nutt wrote:
> >
> >
> > > i want to add some stuff to apps/netutils/webclient.
> > > for example,
> > >
> > > * ability to report http status to the caller
> > > * ability to add some reque
> Is this something we should be concerned about?
Sorry if that came off wrong. I was agreeing with Greg's with the former
statement. Not the latter one.
David
-Original Message-
From: Brennan Ashton [mailto:bash...@brennanashton.com]
Sent: Thursday, July 30, 2020 12:57 PM
To: dev@nutt
while working on BLE stuff with nRF52 I looked around for similar platforms
that could be supported in NuttX. I looked at STM32WB, which is based on a
dual-CPU and supports BLE (as well as various other 2.4GHz protocols). While
not as open as Nordic why publishes the details on the low level
Hi,
while working on BLE stuff with nRF52 I looked around for similar platforms
that could be supported in NuttX. I looked at STM32WB, which is based on a
dual-CPU and supports BLE (as well as various other 2.4GHz protocols). While
not as open as Nordic why publishes the details on the low level
Robert,
I'll take a look this evening and get back to you.
This has run on bare hardware before, as well as in a jailhouse cell,
so it should be fairly close to running on your hardware. I do most
of my testing inside of QEMU since it is much easier for me to attach
the debugger, but I'll see if
On Thu, Jul 30, 2020, 1:35 PM Adam Feuer wrote:
> I didn't know this, but storing artifacts for 90 days is free for open
> source projects on Github.
>
> This action can be used to upload the artifact:
> https://github.com/actions/upload-artifact
>
> Looks like there is a REST API for listing and
I didn't know this, but storing artifacts for 90 days is free for open
source projects on Github.
This action can be used to upload the artifact:
https://github.com/actions/upload-artifact
Looks like there is a REST API for listing and downloading artifacts:
https://developer.github.com/v3/action
Brennan ,
I got your latest code this morning with the pcitest config and have been able
to make it create an iso and run it in qemu. The qemu_pci_init runs and scans
bus 0 which maybe the only bus that qemu is providing. I see the is a function
for mapping pci memory for qemu but there isn't
On Thu, Jul 30, 2020, 1:13 PM Gregory Nutt wrote:
>
> >
> >>> It is a simple matter to see the cost of a PR if we add bloaty
> >>> (https://github.com/google/bloaty) to ci.
> >>>
> >> Great please file the simple PR to add it. This is not trivial as we
> >> need
> >> to manage the artifacts from
It is a simple matter to see the cost of a PR if we add bloaty
(https://github.com/google/bloaty) to ci.
Great please file the simple PR to add it. This is not trivial as we
need
to manage the artifacts from previous builds to do the comparison or
double
the build time. We heard you last t
On Thu, Jul 30, 2020, 1:02 PM Gregory Nutt wrote:
>
> >> It is a simple matter to see the cost of a PR if we add bloaty
> >> (https://github.com/google/bloaty) to ci.
> >>
> > Great please file the simple PR to add it. This is not trivial as we need
> > to manage the artifacts from previous build
It is a simple matter to see the cost of a PR if we add bloaty
(https://github.com/google/bloaty) to ci.
Great please file the simple PR to add it. This is not trivial as we need
to manage the artifacts from previous builds to do the comparison or double
the build time. We heard you last time
On Thu, Jul 30, 2020, 12:40 PM David Sidrane
wrote:
> -1 on more bloat
>
That is not a constructive vote. No one thinks we should have more bloat.
The question is do we need to focus more on this. Some of the changes are
due to shortcuts we have taken in the past that are now causing issues. Th
-1 on more bloat
It is a simple matter to see the cost of a PR if we add bloaty
(https://github.com/google/bloaty) to ci.
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Thursday, July 30, 2020 12:25 PM
To: dev@nuttx.apache.org
Subject: Re: [GitHub] [incubator-nu
But how long does it take you, when the linker tell you, you have over
flowed .text by 256 bytes?
When you overflow memory due to a large number of modest size increases,
there is no way to recover. You are basically screwed because nothing
can really be done. The only way to prevent code
But how long does it take you, when the linker tell you, you have over
flowed .text by 256 bytes?
-Original Message-
From: GitBox [mailto:g...@apache.org]
Sent: Thursday, July 30, 2020 12:13 PM
To: comm...@nuttx.apache.org
Subject: [GitHub] [incubator-nuttx] xiaoxiang781216 commented on a
Brennan,
Thanks for the help thus far. I cloned your branch yesterday afternoon. I
created nuttx.elf files for both qemu-intel64:ostest and qemu-intel64:nsh. I
created iso files using grub as your README.txt stated. And was able to boot
both via qemu this morning. Looks like the OSTEST autom
"Thanks" GMail for sending it twice! :-(
On 7/30/20, Alan Carvalho de Assis wrote:
> Hi Everyone,
>
> In two weeks (Aug 15,16) we will have the N.O.W (NuttX Online Workshop).
>
> To participate please access:
>
> https://nuttx.events/2020/06/15/apply-to-attend-nuttx-online-workshop/
>
> If you ar
Hi Everyone,
In two weeks (Aug 15,16) we will have the N.O.W (NuttX Online Workshop).
To participate please access:
https://nuttx.events/2020/06/15/apply-to-attend-nuttx-online-workshop/
If you are a Speaker you don't need to do it, of course.
BR,
Alan
21 matches
Mail list logo
