[PR] nxgdb/fs: simpifiy inode print and add more command options [nuttx]

2025-02-02 Thread via GitHub
XuNeo opened a new pull request, #15742: URL: https://github.com/apache/nuttx/pull/15742 *Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary ``` Use Inode.__repr__ for print and use single line for all

Re: [PR] nxgdb/irq: add irqinfo command [nuttx]

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

Re: [PR] nxgdb/fs: simpifiy inode print and add more command options [nuttx]

2025-02-02 Thread via GitHub
nuttxpr commented on PR #15742: URL: https://github.com/apache/nuttx/pull/15742#issuecomment-2629402272 [**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues) This PR description, while providing some information,

[PR] nxgdb/memdump: add free command [nuttx]

2025-02-02 Thread via GitHub
XuNeo opened a new pull request, #15744: URL: https://github.com/apache/nuttx/pull/15744 *Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary Similar to nsh command `free`. ``` (gdb) free

[PR] Nxgdb memleak optimization [nuttx]

2025-02-02 Thread via GitHub
XuNeo opened a new pull request, #15745: URL: https://github.com/apache/nuttx/pull/15745 *Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary This PR includes two changes to `nxgdb` memleak command. 1. Fi

Re: [PR] Nxgdb memleak optimization [nuttx]

2025-02-02 Thread via GitHub
nuttxpr commented on PR #15745: URL: https://github.com/apache/nuttx/pull/15745#issuecomment-2629407216 [**\[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] nxgdb/memdump: add free command [nuttx]

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

[PR] nxgdb/irq: add irqinfo command [nuttx]

2025-02-02 Thread via GitHub
XuNeo opened a new pull request, #15743: URL: https://github.com/apache/nuttx/pull/15743 *Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary Similar to nsh command, `irqinfo` shows the registered IRQ ca

Re: [PR] types.h: time_t as int64_t [nuttx]

2025-02-02 Thread via GitHub
cederom commented on PR #14460: URL: https://github.com/apache/nuttx/pull/14460#issuecomment-2629295602 > @raiden00pl: @tmedicci doesn't this change deserve to increase a major version release for NuttX? it may break a lot of small NuttX applications because it will automatically increase t

Re: [I] [RELEASE] 13.0.0 (planning). [nuttx]

2025-02-02 Thread via GitHub
cederom commented on issue #15737: URL: https://github.com/apache/nuttx/issues/15737#issuecomment-2629296220 What should we do with potential changes ready for 13.0.0 and/or stuff that we want in 13 but would break master and short term upcoming 12.x updates? A dedicated branch? Merge to ma

Re: [I] Remove STM32 legacy pinmap [nuttx]

2025-02-02 Thread via GitHub
cederom commented on issue #15432: URL: https://github.com/apache/nuttx/issues/15432#issuecomment-2629551786 Okay I have created list of hardware that I have at hand. Some modern devkits seems to have more powerful STLink MCU than the target MCU 🗡 @raiden00pl please mark the hardware

[I] [DRUNX] Hardware Database [nuttx]

2025-02-02 Thread via GitHub
cederom opened a new issue, #15746: URL: https://github.com/apache/nuttx/issues/15746 ### Description It would be good to know who has what hardware available at hand for initial DRUNX development and testing, thus the list below based on architecture, please update with the hardware