Hi all,
I noticed that when spawning a new task/process from a file in
nsh_fileapps, the scheduler is locked prior to calling posix_spawn(), which
does the file loading into memory etc.
I noticed one issue with this; when the file size is large (in the order of
MB) the scheduler is locked for ver
On Wed, Oct 25, 2023 at 5:16 AM Ville Juven wrote:
> Hi all,
>
> I noticed that when spawning a new task/process from a file in
> nsh_fileapps, the scheduler is locked prior to calling posix_spawn(), which
> does the file loading into memory etc.
>
> I noticed one issue with this; when the file s
On 10/25/23, Nathan Hartman wrote:
> On Wed, Oct 25, 2023 at 5:16 AM Ville Juven wrote:
>
>> Hi all,
>>
>> I noticed that when spawning a new task/process from a file in
>> nsh_fileapps, the scheduler is locked prior to calling posix_spawn(),
>> which
>> does the file loading into memory etc.
>>
On 10/25/2023 8:18 AM, Alan C. Assis wrote:
On 10/25/23, Nathan Hartman wrote:
On Wed, Oct 25, 2023 at 5:16 AM Ville Juven wrote:
Hi all,
I noticed that when spawning a new task/process from a file in
nsh_fileapps, the scheduler is locked prior to calling posix_spawn(),
which
does the file
On 10/25/2023 8:48 AM, Gregory Nutt wrote:
On 10/25/2023 8:18 AM, Alan C. Assis wrote:
On 10/25/23, Nathan Hartman wrote:
On Wed, Oct 25, 2023 at 5:16 AM Ville Juven wrote:
Hi all,
I noticed that when spawning a new task/process from a file in
nsh_fileapps, the scheduler is locked prior to
Hi,
Thanks for the responses, they are very much appreciated.
I suspected that the scheduler lock can be removed without too severe side
effects (I made a PR of it already). I made a PR of removing it from
nsh_fileapps already since I think that is potentially a more critical
place to fix due to
Hi all,
forgive my ignorance, I’ve just started diving into networking topics
(including handling connections via Berkeley sockets). My final goal is to
make my device reachable via two separate IP addresses with a single PHY.
Once there are two IP addresses set up I'd bind to each specific addr
On 10/25/2023 9:27 AM, Matthias Roosz wrote:
Hi all,
forgive my ignorance, I’ve just started diving into networking topics
(including handling connections via Berkeley sockets). My final goal is to
make my device reachable via two separate IP addresses with a single PHY.
Once there are two IP
Hi all,
forgive my ignorance, I've just started diving into networking topics
(including handling connections via Berkley sockets). My final goal is to make
my device reachable via two separate IP addresses with a single PHY. Once there
are two IPs set up I'd bind to each specific address to ge
Hello,
Actually, looking closer at the samd21 datasheet, my led pin can be
configured in SPI MOSI.
In board/samd2l2/arduino-m0/src/ I added sam_ws2812.c, sam_ws2812.h which
are a adapted copy of the stm32 version.
Everything compiles but on "nsh> ls /dev", I can see that the led device
(/dev/leds
Hi Bert,
Please look your System.map and confirm it is generating the function
board_ws2812_initialize(). Something it is not even included because
some missing configuration.
You enabled DEBUG LED INFO, show you should see some messages in the
console if it was called, see: drivers/leds/ws2812.c
Hi Matthias,
I agree with Gregory's opinion, if you want to do the same thing on NuttX as
you do on Linux, you'll need both:
1. Support multiple IP addresses in the device structure
2. Support the alias like 'eth0:0' because the ioctl of IPv4 address is
designed to set one address per interface,
12 matches
Mail list logo
