(nuttx) branch master updated (34bde7b80a -> 35e5612bce)

2025-02-11 Thread archer
This is an automated email from the ASF dual-hosted git repository. archer pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git from 34bde7b80a qemu/armv7a: register cfi flash add b1bd1b292e arch/armv7-r: fix irq.h for PROTECTED mode add f195

Re: [PR] arch/armv7-r: PROTECTED mode support (1/2) [nuttx]

2025-02-11 Thread via GitHub
anchao merged PR #15800: URL: https://github.com/apache/nuttx/pull/15800 -- 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...@nuttx.apach

Re: [PR] arch/armv7-r: PROTECTED mode support (1/2) [nuttx]

2025-02-11 Thread via GitHub
xiaoxiang781216 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950693151 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + s

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15815: URL: https://github.com/apache/nuttx/pull/15815#issuecomment-2650709774 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) Yes, this PR description meets the NuttX requirements.

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
xiaoxiang781216 commented on code in PR #15815: URL: https://github.com/apache/nuttx/pull/15815#discussion_r1950782741 ## arch/risc-v/src/common/riscv_backtrace.c: ## @@ -150,17 +163,10 @@ int up_backtrace(struct tcb_s *tcb, void **buffer, int size, int skip) { if (

Re: [I] [FEATURE] Should we extend fastboot oem to support executing custom commands? [nuttx-apps]

2025-02-11 Thread via GitHub
JianyuWang0623 commented on issue #2991: URL: https://github.com/apache/nuttx-apps/issues/2991#issuecomment-2650910731 CC @Donny9 @yangsong8-ai -- 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

[PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti opened a new pull request, #15815: URL: https://github.com/apache/nuttx/pull/15815 ## Summary This PR adds support for backtrace on RISC-V on certain build settings explained below. Up to this point, it was not printing anything useful during crashes. ## Impact

Re: [PR] mtd/w25q: ensure the correct behavior if erase sector fails [nuttx]

2025-02-11 Thread via GitHub
acassis commented on code in PR #15812: URL: https://github.com/apache/nuttx/pull/15812#discussion_r1950859784 ## drivers/mtd/w25qxxxjv.c: ## @@ -976,10 +976,10 @@ static int w25qxxxjv_erase_sector(FAR struct w25qxxxjv_dev_s *priv, } status = w25qxxxjv_read_status(pri

Re: [PR] mtd/w25q: ensure the correct behavior if erase sector fails [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15812: URL: https://github.com/apache/nuttx/pull/15812#issuecomment-2650481790 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) Yes, this PR appears to meet the NuttX requirements, al

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2650593697 Jus curious will the existing document on rpproxy and rpserver needs be updated? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
acassis commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2651362490 @OceanfromXiaomi please explain the pros and cons of this approach. Seems like now it will be limited to a single pollfds notification. It could work fine for simple applications, but for

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
linguini1 commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2651400337 Can you provide more description of how you tested? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abov

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
raiden00pl commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2651434804 @acassis this change moves `cd_fds` to `struct can_reader_s` which is allocated dynamically in `init_can_reader()` after each `open()`. So the number of poll waiters is not limited.

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
TimJTi commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2651459716 I have a board with CAN, and use polling although with just one poll waiter. I will try and find time to do a quick works/doesn't work check tomorrow if that's of help? -- This is an au

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti commented on code in PR #15815: URL: https://github.com/apache/nuttx/pull/15815#discussion_r1951225283 ## arch/risc-v/src/common/riscv_exception_common.S: ## @@ -207,25 +207,46 @@ handle_irq: .cfi_offset x2, 8 /* Toolchain not support macro, is REG_

Re: [PR] drivers/sensors: Added uORB driver for LSM6DSO32 IMU. [nuttx]

2025-02-11 Thread via GitHub
xiaoxiang781216 commented on PR #15789: URL: https://github.com/apache/nuttx/pull/15789#issuecomment-2650589585 > @acassis during the 12.8.0 stabilization period there were some conflicts that made me ask for this change. If we plan to maintain the LTS release we should make it manageable.

[PR] arch/armv7-r: PROTECTED mode support (2/2) [nuttx]

2025-02-11 Thread via GitHub
yf13 opened a new pull request, #15813: URL: https://github.com/apache/nuttx/pull/15813 ## Summary This is the board specific part of armv7-r PROTECTED mode support on QEMU. It was splitted from pull#15800, which contains more relevant information. ## Impacts Adding PROT

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
lupyuen commented on PR #15815: URL: https://github.com/apache/nuttx/pull/15815#issuecomment-2650751700 @nuttxpr test milkv_duos:nsh -- 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 c

Re: [PR] DOC: Fix documentation to include checkpatch.sh [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti commented on code in PR #15794: URL: https://github.com/apache/nuttx/pull/15794#discussion_r1950811666 ## Documentation/contributing/coding_style.rst: ## @@ -12,6 +12,25 @@ for conformance to the coding style, you should use the `nxstyle <#nxstyle>`_ tool included

Re: [PR] DOC: Fix documentation to include checkpatch.sh [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti commented on code in PR #15794: URL: https://github.com/apache/nuttx/pull/15794#discussion_r1950811666 ## Documentation/contributing/coding_style.rst: ## @@ -12,6 +12,25 @@ for conformance to the coding style, you should use the `nxstyle <#nxstyle>`_ tool included

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti commented on code in PR #15815: URL: https://github.com/apache/nuttx/pull/15815#discussion_r1950818774 ## arch/risc-v/src/common/riscv_backtrace.c: ## @@ -150,17 +163,10 @@ int up_backtrace(struct tcb_s *tcb, void **buffer, int size, int skip) { if (up_

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti commented on code in PR #15815: URL: https://github.com/apache/nuttx/pull/15815#discussion_r1950818774 ## arch/risc-v/src/common/riscv_backtrace.c: ## @@ -150,17 +163,10 @@ int up_backtrace(struct tcb_s *tcb, void **buffer, int size, int skip) { if (up_

Re: [PR] esp32: Add support for espnow based pktradio [nuttx]

2025-02-11 Thread via GitHub
tmedicci commented on PR #15732: URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2650775403 > Hi @tmedicci thanks for the merge. > > As I am new to NuttX I don't know all the rules, but should I have marked this new feature as `EXPERIMENTAL`? > > I would like to fu

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15815: URL: https://github.com/apache/nuttx/pull/15815#issuecomment-2650783082 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+15779&type=issues) Build and Test Successful (milkv_duos:nsh) https://gitlab.co

[PR] STM32L4: Fix all boards to support proper stm32_bringup.c [nuttx]

2025-02-11 Thread via GitHub
acassis opened a new pull request, #15817: URL: https://github.com/apache/nuttx/pull/15817 ## Summary Many STM32L4 boards are missing stm32_bringup.c. That confusion was created when stm32_appinit.c was created. It introduced a new way to do the board initialization without depen

[PR] xtensa/esp32s3: use common Espressif wireless source [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti opened a new pull request, #15816: URL: https://github.com/apache/nuttx/pull/15816 ## Summary This PR modifies ESP32S3 to use WiFi source code from the common layer, which is already used by ESP32S2. KConfig prefixes such as `ESP32S3_*` are replaced with `ESPRESSIF

Re: [PR] xtensa/esp32s3: use common Espressif wireless source [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15816: URL: https://github.com/apache/nuttx/pull/15816#issuecomment-2651832926 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) This PR mostly meets the NuttX requirements but is miss

Re: [PR] STM32L4: Fix all boards to support proper stm32_bringup.c [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15817: URL: https://github.com/apache/nuttx/pull/15817#issuecomment-2651865282 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) No, this PR does not fully meet the NuttX requirements.

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on PR #15800: URL: https://github.com/apache/nuttx/pull/15800#issuecomment-2650092626 @anchao now that CI check passed, I am about to do the following clean ups: - Reduce the scope of this PR to `arch/arm`. and I will guard ARM_THUMB with PROTECTED as you suggested.

Re: [PR] Thermal: Add support for passive trip point [nuttx]

2025-02-11 Thread via GitHub
JianyuWang0623 commented on PR #15811: URL: https://github.com/apache/nuttx/pull/15811#issuecomment-2650176716 @Donny9 Could you review this PR please? -- 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 g

Re: [PR] max32690 port [nuttx]

2025-02-11 Thread via GitHub
jerpelea commented on PR #15793: URL: https://github.com/apache/nuttx/pull/15793#issuecomment-2650110506 please add in the commit title the area impacted by the commit ex: arch/arm/max326xx -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [PR] arch/armv7-r: PROTECTED mode support (1/2) [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950195337 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

[PR] Thermal: Add support for passive trip point [nuttx]

2025-02-11 Thread via GitHub
JianyuWang0623 opened a new pull request, #15811: URL: https://github.com/apache/nuttx/pull/15811 ## Summary 1. Add support for passive trip point. Spliting `THERMAL_NORMAL` to `THERMAL_ACTIVE` and `THERMAL_PASSIVE`, to support different update intervals for thermal zone, mainly fo

Re: [PR] max32690 port [nuttx]

2025-02-11 Thread via GitHub
lordrasmus commented on PR #15793: URL: https://github.com/apache/nuttx/pull/15793#issuecomment-2650113993 ok i added some descriptions -- 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 specifi

Re: [PR] max32690 port [nuttx]

2025-02-11 Thread via GitHub
lordrasmus commented on PR #15793: URL: https://github.com/apache/nuttx/pull/15793#issuecomment-2650126587 like this ? -- 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 un

Re: [PR] Thermal: Add support for passive trip point [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15811: URL: https://github.com/apache/nuttx/pull/15811#issuecomment-2650116928 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) This PR mostly meets the NuttX requirements, but could

Re: [PR] esp32: Add support for espnow based pktradio [nuttx]

2025-02-11 Thread via GitHub
jerpelea commented on PR #15732: URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2650102724 > > > please split arch and documentation in separate PR if we try to maintain LTS releases this is a requirement > > > > > > In this case, @jerpelea , It makes sense to keep t

Re: [PR] Thermal: Add support for passive trip point [nuttx]

2025-02-11 Thread via GitHub
JianyuWang0623 commented on PR #15811: URL: https://github.com/apache/nuttx/pull/15811#issuecomment-2650129109 > drivers/thermal/dummy: Add another passive cooling device @jerpelea Done, thank you. -- This is an automated message from the Apache Git Service. To respond to the messa

Re: [PR] drivers/sensors: Added uORB driver for LSM6DSO32 IMU. [nuttx]

2025-02-11 Thread via GitHub
jerpelea commented on PR #15789: URL: https://github.com/apache/nuttx/pull/15789#issuecomment-2650154526 @acassis during the 12.8.0 stabilization period there were some conflicts that made me ask for this change. If we plan to maintain the LTS release we should make it manageable. Unless we

Re: [PR] esp32: Add support for espnow based pktradio [nuttx]

2025-02-11 Thread via GitHub
jerpelea commented on PR #15732: URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2650165139 we should discuss on the dev mailing list I will start a new thread -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub a

Re: [PR] esp32: Add support for espnow based pktradio [nuttx]

2025-02-11 Thread via GitHub
Laczen commented on PR #15732: URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2650157349 > > > > please split arch and documentation in separate PR if we try to maintain LTS releases this is a requirement > > > > > > > > > In this case, @jerpelea , It makes sense to

Re: [PR] drivers/thermal: Add support for passive trip point [nuttx]

2025-02-11 Thread via GitHub
JianyuWang0623 commented on PR #15811: URL: https://github.com/apache/nuttx/pull/15811#issuecomment-2650320589 > please add a commit message describing why you added the change Mainly for low-power, as the "Summary" say. Can save power by reducing times the worker was invoked.

Re: [PR] arch/xtensa: unify WiFi source code for ESP32|S2|S3 [nuttx]

2025-02-11 Thread via GitHub
jerpelea commented on PR #15749: URL: https://github.com/apache/nuttx/pull/15749#issuecomment-2650229232 @fdcavalcanti sorry for not being clear -- 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 th

(nuttx) 01/04: drivers/mtd: cfi-flash driver

2025-02-11 Thread archer
This is an automated email from the ASF dual-hosted git repository. archer pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git commit ac019bbfa2707c7eeddcd8b3be2294c9a75b5c4e Author: zhengyu9 AuthorDate: Fri Jul 26 15:38:00 2024 +0800 drivers/mtd: cf

Re: [PR] Support Common Flash Interface (CFI) FLASH [nuttx]

2025-02-11 Thread via GitHub
anchao merged PR #15802: URL: https://github.com/apache/nuttx/pull/15802 -- 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...@nuttx.apach

(nuttx) branch master updated (405287081d -> 34bde7b80a)

2025-02-11 Thread archer
This is an automated email from the ASF dual-hosted git repository. archer pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git from 405287081d boards/arm Add support to Seeed Xiao nRF52840 Board new ac019bbfa2 drivers/mtd: cfi-flash driver n

(nuttx) 03/04: qemu/armv7-a: adjust flash size to free area to register cfi flash

2025-02-11 Thread archer
This is an automated email from the ASF dual-hosted git repository. archer pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git commit ef24233501298d3a349a66a1a2f4a42978851dc7 Author: dongjiuzhu1 AuthorDate: Sat Feb 8 12:11:46 2025 +0800 qemu/armv7-a:

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
anchao commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950387671 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950385260 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM_T

Re: [PR] arch/armv7-r: PROTECTED mode support [nuttx]

2025-02-11 Thread via GitHub
anchao commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950396819 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM

Re: [I] [BUG] [nuttx]

2025-02-11 Thread via GitHub
simbit18 commented on issue #15807: URL: https://github.com/apache/nuttx/issues/15807#issuecomment-2650197438 hi @Justin-Morrison-github it seems related to wrong path ``` apps/examples/hello_rust/Kconfig' not found (in 'source "/home/morri/InSpace/InSpace-Nuttx/apps/examples/hello

Re: [PR] drivers/thermal: Add support for passive trip point [nuttx]

2025-02-11 Thread via GitHub
Donny9 commented on code in PR #15811: URL: https://github.com/apache/nuttx/pull/15811#discussion_r1950473290 ## drivers/thermal/thermal_core.c: ## @@ -893,8 +896,27 @@ void thermal_zone_device_update(FAR struct thermal_zone_device_s *zdev) } } + /* Update work

[PR] mtd/w25q: ensure the correct behavior if erase sector fails [nuttx]

2025-02-11 Thread via GitHub
michallenc opened a new pull request, #15812: URL: https://github.com/apache/nuttx/pull/15812 ## Summary Function `w25qxxxjv_erase` wasn't correctly handling an error in `w25qxxxjv_erase_sector` call and was returning success even on failure. Moreover this change does not return `EBUSY`

Re: [PR] max32690 port [nuttx]

2025-02-11 Thread via GitHub
lordrasmus commented on PR #15793: URL: https://github.com/apache/nuttx/pull/15793#issuecomment-2650427103 so i think i heave learned how to contribute to nuttx will you merge this and close this pull request or should i add the next driver in this pr ? -- This is an automated mess

Re: [PR] max32690 port [nuttx]

2025-02-11 Thread via GitHub
lupyuen commented on PR #15793: URL: https://github.com/apache/nuttx/pull/15793#issuecomment-2650442286 This PR will be merged in a while. You can prepare the next driver in a new PR. Thanks :-) -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [PR] drivers/sensors: Added uORB driver for LSM6DSO32 IMU. [nuttx]

2025-02-11 Thread via GitHub
raiden00pl commented on PR #15789: URL: https://github.com/apache/nuttx/pull/15789#issuecomment-2651532791 @jerpelea If we don't have the resources to deal with LTS, why do it at all? making life difficult for (few) contributors is a tragic solution. Another issue is that some changes must

Re: [PR] risc-v/backtrace: Support backtrace dump during IRQ [nuttx]

2025-02-11 Thread via GitHub
fdcavalcanti commented on PR #15815: URL: https://github.com/apache/nuttx/pull/15815#issuecomment-2651507703 I have added a backtrace example output on the PR description. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us

Re: [PR] Initial standalone sx126x driver [WIP] [nuttx]

2025-02-11 Thread via GitHub
keever50 commented on PR #15795: URL: https://github.com/apache/nuttx/pull/15795#issuecomment-2651584456 hm, i dont think that squashed, or did it -- 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

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
acassis commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2651600387 Thank @raiden00pl ! I missed that open part, the only thing that was making me believe it still creating more notifications was: ``` list_for_every(&dev->cd_readers, node)

Re: [PR] arch/armv7-r: PROTECTED mode support (2/2) [nuttx]

2025-02-11 Thread via GitHub
nuttxpr commented on PR #15813: URL: https://github.com/apache/nuttx/pull/15813#issuecomment-2650602509 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) No, this PR description does not fully meet the NuttX r

Re: [PR] arch/armv7-r: PROTECTED mode support (1/2) [nuttx]

2025-02-11 Thread via GitHub
anchao commented on code in PR #15800: URL: https://github.com/apache/nuttx/pull/15800#discussion_r1950700737 ## arch/arm/Kconfig: ## @@ -982,6 +982,7 @@ config ARCH_ARMV7R default n select ARCH_HAVE_CPUINFO select ARCH_HAVE_PERF_EVENTS + select ARM

[PR] littlefs/cmake: fix compilation flag issue [nuttx]

2025-02-11 Thread via GitHub
yf13 opened a new pull request, #15814: URL: https://github.com/apache/nuttx/pull/15814 ## Summary This fixes a build issue on Ubuntu 22.04 with cmake 3.22.1 for `qemu-armv7a:rpproxy_ivmshmem`: ``` $ cmake --version cmake version 3.22.1 $ ninja [129/1346] Buildi

Re: [PR] mtd/w25q: ensure the correct behavior if erase sector fails [nuttx]

2025-02-11 Thread via GitHub
michallenc commented on code in PR #15812: URL: https://github.com/apache/nuttx/pull/15812#discussion_r1950912832 ## drivers/mtd/w25qxxxjv.c: ## @@ -976,10 +976,10 @@ static int w25qxxxjv_erase_sector(FAR struct w25qxxxjv_dev_s *priv, } status = w25qxxxjv_read_status(

[I] [FEATURE] Should we extend fastboot oem to support executing custom commands? [nuttx-apps]

2025-02-11 Thread via GitHub
JianyuWang0623 opened a new issue, #2991: URL: https://github.com/apache/nuttx-apps/issues/2991 ### Is your feature request related to a problem? Please describe. Should we extend "fastboot oem" to support executing custom commands for test or debug, such as, make ram disk: `fastboot

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
anchao commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2650950420 > Jus curious if the existing document about `rpproxy_ivshmem` and `rpserver_ivshmem` needs be updated as well? Will submit in separate PR, please help approve if there is no any que

Re: [PR] DOC: Fix documentation to include checkpatch.sh [nuttx]

2025-02-11 Thread via GitHub
LuchianMihai commented on PR #15794: URL: https://github.com/apache/nuttx/pull/15794#issuecomment-2651205383 > > > > Hi @acassis, On the same page, an paragraph before, talks about nxstyle, which can be used to do the same thing. Should we move that sentence to your new heading as well?

Re: [I] [FEATURE] Should we extend fastboot oem to support executing custom commands? [nuttx-apps]

2025-02-11 Thread via GitHub
cederom commented on issue #2991: URL: https://github.com/apache/nuttx-apps/issues/2991#issuecomment-2651101113 I like the idea :-) Should it be build-time selectable / configurable? It may introduce security issue when commands execution is possible at this point on production systems? :-)

Re: [I] [FEATURE] Should we extend fastboot oem to support executing custom commands? [nuttx-apps]

2025-02-11 Thread via GitHub
JianyuWang0623 commented on issue #2991: URL: https://github.com/apache/nuttx-apps/issues/2991#issuecomment-2651113354 > I like the idea :-) Should it be build-time selectable / configurable? It may introduce security issue when commands execution is possible at this point on production sys

Re: [PR] DOC: Fix documentation to include checkpatch.sh [nuttx]

2025-02-11 Thread via GitHub
acassis commented on code in PR #15794: URL: https://github.com/apache/nuttx/pull/15794#discussion_r1951057934 ## Documentation/contributing/coding_style.rst: ## @@ -12,6 +12,25 @@ for conformance to the coding style, you should use the `nxstyle <#nxstyle>`_ tool included unde

Re: [PR] DOC: Fix documentation to include checkpatch.sh [nuttx]

2025-02-11 Thread via GitHub
acassis commented on PR #15794: URL: https://github.com/apache/nuttx/pull/15794#issuecomment-2651157087 > > > Hi @acassis, On the same page, an paragraph before, talks about nxstyle, which can be used to do the same thing. Should we move that sentence to your new heading as well? > >

(nuttx) branch master updated: littlefs/cmake: fix build issue

2025-02-11 Thread archer
This is an automated email from the ASF dual-hosted git repository. archer pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git The following commit(s) were added to refs/heads/master by this push: new 225197b779 littlefs/cmake: fix build issue 225197

Re: [PR] littlefs/cmake: fix compilation flag issue [nuttx]

2025-02-11 Thread via GitHub
anchao merged PR #15814: URL: https://github.com/apache/nuttx/pull/15814 -- 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...@nuttx.apach

(nuttx) branch master updated (225197b779 -> 381d3fe64f)

2025-02-11 Thread acassis
This is an automated email from the ASF dual-hosted git repository. acassis pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git from 225197b779 littlefs/cmake: fix build issue add a4cfd5f9da arch/arm/max326xx: add max32690 irq and peripheral cloc

Re: [PR] max32690 port [nuttx]

2025-02-11 Thread via GitHub
acassis merged PR #15793: URL: https://github.com/apache/nuttx/pull/15793 -- 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...@nuttx.apac

Re: [PR] drivers/sensors: Added uORB driver for LSM6DSO32 IMU. [nuttx]

2025-02-11 Thread via GitHub
acassis commented on PR #15789: URL: https://github.com/apache/nuttx/pull/15789#issuecomment-2651180321 @jerpelea @xiaoxiang781216 maybe it is worth to investigate how other projects that have LTS are solving it. Forcing our (few) contributors to create a single PR for each modified are see

Re: [PR] Initial standalone sx126x driver [WIP] [nuttx]

2025-02-11 Thread via GitHub
keever50 commented on PR #15795: URL: https://github.com/apache/nuttx/pull/15795#issuecomment-2651625180 I am not sure if i should keep squashing it with force pushing on every change. Tell me if i am doing something wrong. Learning new things -- This is an automated message from the Apac

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
OceanfromXiaomi commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2652511636 > I have a board with CAN, and use polling although with just one poll waiter. I will try and find time to do a quick works/doesn't work check tomorrow if that's of help? H

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
anchao commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2652747461 > > @anchao, thanks. I tried both qemu-armv7a and qemu-armv8a on Ubuntu 22.04 with QEMU v6.2. rpsock stream block test sessions all complete. only qemu-armv8a server side doesn't return ba

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
anchao commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2652745209 > @anchao, thanks. I tried both qemu-armv7a and qemu-armv8a on Ubuntu 22.04 with QEMU v6.2. rpsock stream block test sessions all complete. only qemu-armv8a server side doesn't return back

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
OceanfromXiaomi commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2652503094 > @OceanfromXiaomi please explain the pros and cons of this approach. Seems like now it will be limited to a single pollfds notification. It could work fine for simple application

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
OceanfromXiaomi commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2652503984 > Can you provide more description of how you tested? OK -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub an

Re: [PR] nuttx/can: Modify poll logic to bind can_reader_s and pollfd. [nuttx]

2025-02-11 Thread via GitHub
OceanfromXiaomi commented on PR #15809: URL: https://github.com/apache/nuttx/pull/15809#issuecomment-2652579109 @acassis @linguini1 @raiden00pl @TimJTi Hi, teachers, please check my latest comments. -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2652627278 @anchao, I tried both qemu-armv7a and qemu-armv8a on Ubuntu 22.04 with QEMU v6.2. rpsock stream block test sessions all complete. only qemu-armv8a server side doesn't return back to nsh.

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
yf13 commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2652628233 @anchao, I tried both qemu-armv7a and qemu-armv8a on Ubuntu 22.04 with QEMU v6.2. rpsock stream block test sessions all complete. only qemu-armv8a server side doesn't return back to nsh.

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
anchao commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2652648108 > @anchao, I tried both qemu-armv7a and qemu-armv8a on Ubuntu 22.04 with QEMU v6.2. rpsock stream block test sessions all complete. only qemu-armv8a server side doesn't return back to nsh.

Re: [PR] qemu/ivshmem: switch proxy/server roles [nuttx]

2025-02-11 Thread via GitHub
anchao commented on PR #15810: URL: https://github.com/apache/nuttx/pull/15810#issuecomment-2652658030 > @anchao, thanks. I tried both qemu-armv7a and qemu-armv8a on Ubuntu 22.04 with QEMU v6.2. rpsock stream block test sessions all complete. only qemu-armv8a server side doesn't return back

Re: [PR] Initial standalone sx126x driver [WIP] [nuttx]

2025-02-11 Thread via GitHub
acassis commented on code in PR #15795: URL: https://github.com/apache/nuttx/pull/15795#discussion_r1951504067 ## drivers/wireless/lpwan/sx126x/sx126x.c: ## @@ -0,0 +1,1008 @@ +/ + * drivers/wireless/lpw

Re: [PR] Initial standalone sx126x driver [WIP] [nuttx]

2025-02-11 Thread via GitHub
keever50 commented on code in PR #15795: URL: https://github.com/apache/nuttx/pull/15795#discussion_r1951536782 ## drivers/wireless/lpwan/sx126x/sx126x.c: ## @@ -0,0 +1,1008 @@ +/ + * drivers/wireless/lp

Re: [PR] Initial standalone sx126x driver [WIP] [nuttx]

2025-02-11 Thread via GitHub
keever50 commented on code in PR #15795: URL: https://github.com/apache/nuttx/pull/15795#discussion_r1951536782 ## drivers/wireless/lpwan/sx126x/sx126x.c: ## @@ -0,0 +1,1008 @@ +/ + * drivers/wireless/lp

Re: [PR] qemu-armv7a and armv8a Ivshmem configs update [nuttx]

2025-02-11 Thread via GitHub
CV-Bowen commented on PR #15818: URL: https://github.com/apache/nuttx/pull/15818#issuecomment-2652919887 @anchao @acassis @xiaoxiang781216 @GUIDINGLI Could you help review this PR? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[PR] qemu-armv7a and armv8a Ivshmem configs update [nuttx]

2025-02-11 Thread via GitHub
CV-Bowen opened a new pull request, #15818: URL: https://github.com/apache/nuttx/pull/15818 ## Summary Author: Bowen Wang Date: Wed Feb 12 15:51:30 2025 +0800 arm64/qemu-armv8a: optimize the proxy and server configs rpserver should be the master core, so mod