yf13 commented on PR #15624:
URL: https://github.com/apache/nuttx/pull/15624#issuecomment-2613710524
> Did you try it on these boards?
@acassis, no I didn't because I couldn't. Seeing that `nx_start()` has about
73+ uses in C and 10 in ASM, plus the comment in `armv7-r/arm_head.S` and
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/nuttx-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 81d0de3ba0 Publishing web: c9485a
cederom commented on issue #12381:
URL: https://github.com/apache/nuttx/issues/12381#issuecomment-2613609732
Hey there @michallenc :-) Yes I have sent already a GSoC 2025 related email
some time ago and reminder right now to our dev@ mailing list where proposals
can be reported :-)
H
cederom commented on PR #2974:
URL: https://github.com/apache/nuttx-apps/pull/2974#issuecomment-2613604297
Thank you @txy-21 :-) Would you like to move selected applications to
`apps/system` right now or you have patch set ready and prefer to move them
after `apps/testing` is reorganized ba
acassis commented on PR #15624:
URL: https://github.com/apache/nuttx/pull/15624#issuecomment-2613318964
@yf13 I think it will impact at least these boards:
pcDuino
Beagle Bone Black
giant-board
jupiter-nano
sama5d3-xplained
Did you try it on these boards?
I ha
artdeell closed issue #15689: [HELP] Questions about NuttX on the ESP32
URL: https://github.com/apache/nuttx/issues/15689
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To uns
artdeell opened a new issue, #15690:
URL: https://github.com/apache/nuttx/issues/15690
### Description / Steps to reproduce the issue
Debian ships an outdated version of esptool (4.7.0), so i use pipx to have a
more up-to-date version of it installed. Sadly it appears that the
check_
artdeell commented on issue #15689:
URL: https://github.com/apache/nuttx/issues/15689#issuecomment-2613205247
Alright, thank you! I'll keep exploring and see what I find.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
michallenc commented on issue #12381:
URL: https://github.com/apache/nuttx/issues/12381#issuecomment-2613180783
@acassis @cederom Hey guys, do you know how we stand with Apache on Google
Summer of Code this year? I think the proposals will be open in the near future
and this could be an int
michallenc commented on issue #12381:
URL: https://github.com/apache/nuttx/issues/12381#issuecomment-2613173328
We also have to think about different frequencies for channels. That is not
supported in all MCUs, but some have the capability to set a different
frequency for different channels
tmedicci commented on issue #15689:
URL: https://github.com/apache/nuttx/issues/15689#issuecomment-2613157082
Hi @artdeell !
Glad to hear that you are considering using the ESP32 on NuttX. Regarding
your questions:
> * How to properly use `make menuconfig`? Yes, the men
artdeell opened a new issue, #15689:
URL: https://github.com/apache/nuttx/issues/15689
### Description
I have no proper RTOS and ESP32 experience (but I have worked with an
ESP8266 on a basic level before), and I wanted to try NuttX. So i wanted to ask
some newbie questions that i di
hartmannathan commented on code in PR #15484:
URL: https://github.com/apache/nuttx/pull/15484#discussion_r1928894563
##
mm/Kconfig:
##
@@ -69,6 +69,14 @@ config MM_DEFAULT_ALIGNMENT
memory default alignment is equal to sizoef(uintptr), if this
value
acassis commented on code in PR #15657:
URL: https://github.com/apache/nuttx/pull/15657#discussion_r1928768548
##
audio/Kconfig:
##
@@ -277,4 +277,10 @@ config AUDIO_FONT
endif
+config AUDIO_MAX_APPS
+ int "Number of applications that can use upperhalf driver meanwhil
ppisa commented on PR #14759:
URL: https://github.com/apache/nuttx/pull/14759#issuecomment-2612263149
I agree with pushing this part common header. I am not sure if the name
shortening is ideal. May it be `can_common.h`.
It can be in separate C file which is build for both, SocketCAN and
hujun260 closed pull request #15687: Revert "sched/wqueue: some minor improve
to reduce sched_lock range"
URL: https://github.com/apache/nuttx/pull/15687
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
ppisa commented on issue #15567:
URL: https://github.com/apache/nuttx/issues/15567#issuecomment-2612183390
In addition, NuttX seems to have reasonable support for Microchip's
PolarFire SoCs. I have BeagleV-Fire SBCs based on the chip. I tested Linux and
RTEMS on it, plan NuttX too and plan
ppisa commented on issue #15567:
URL: https://github.com/apache/nuttx/issues/15567#issuecomment-2612168607
> +1 for common bittiming calculation interface. Names with `nx_` prefix are
OK.
Great, I will discuss that with @michallenc and we would reuse knowledge or
code (license is OK
ppisa commented on issue #12381:
URL: https://github.com/apache/nuttx/issues/12381#issuecomment-2612087712
@raiden00pl, @michallenc I only confirm that design of universal API for all
purposes is problematic. In this respect and respect of hardware defined
grouping, I am OK with actual desi
xiaoxiang781216 commented on code in PR #2974:
URL: https://github.com/apache/nuttx-apps/pull/2974#discussion_r1928394327
##
testing/sched/atomic/Makefile:
##
@@ -1,5 +1,5 @@
-# apps/testing/atomic/Mak
anchao commented on PR #15684:
URL: https://github.com/apache/nuttx/pull/15684#issuecomment-2612062152
> @anchao your understand isn't fully correct, please reference this
document: https://docs.kernel.org/locking/locktypes.html NuttX recent change
make the behaivour same as Linux when PREE
xiaoxiang781216 commented on code in PR #15687:
URL: https://github.com/apache/nuttx/pull/15687#discussion_r1928390392
##
sched/wqueue/kwork_queue.c:
##
@@ -151,6 +152,7 @@ int work_queue_wq(FAR struct kwork_wqueue_s *wqueue,
*/
flags = spin_lock_irqsave(&wqueue->lock);
xiaoxiang781216 merged PR #15686:
URL: https://github.com/apache/nuttx/pull/15686
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nu
anchao commented on PR #15687:
URL: https://github.com/apache/nuttx/pull/15687#issuecomment-2612039211
@hujun260 spin_lock already has the function of sched_lock. could the
sched_lock/unlock here be deleted directly?
--
This is an automated message from the Apache Git Service.
To respond
Laczen commented on PR #15604:
URL: https://github.com/apache/nuttx/pull/15604#issuecomment-2612027178
> > I have seen that there is quite some discussion about the use of
read/readv and write/writev. Why does NuttX use uio for readv/writev instead of
the classic iovec and iovcnt ?
>
25 matches
Mail list logo
