Re: [EXT] Re: [PROPOSAL] New nxstyle tool roadmap

2025-03-24 Thread Alan C. Assis
But changing from GNU to Altman (removing 2 "half" indentation spaces) could fall on this category: ``No "revolutionary" changes to the coding standard (but perhaps some "evolutionary" changes).'' BR, Alan On Wed, Mar 19, 2025 at 10:24 AM Gregory Nutt wrote: > Coding style change are discuss

Re: Discuss NXBoot

2025-03-24 Thread Alan C. Assis
Hi Tim, Yes, these suggestions make sense! I think for NXBoot should be nice to have the option to disable features that were used for minsh board profile: # # RTOS Features # CONFIG_DISABLE_SIGNALS=y # # Files and I/O # CONFIG_SDCLONE_DISABLE=y CONFIG_NFILE_DESCRIPTORS=0 CONFIG_NFILE_STREAMS=0

Discuss NXBoot

2025-03-24 Thread Tim Hardisty
I am just starting to use NXboot (having migrated from Uboot, then to MCUboot, and finally settled on NXboot) and I'm wondering whether it would benefit from some changes and/or enhancements now I've used all three. Thoughts, observations, suggestions welcomed. In no particular order: 1. Uboo

Re: Can NSEC_PER_USEC in clock.h be changed to 1000L?

2025-03-24 Thread Lwazi Dube
On Mon, 24 Mar 2025 at 05:00, Sebastien Lorquet wrote: > Hello, > > I also dont have a github account (anymore), also for reasons. > What are "reasons"? Is this about AI training?

Re: Double erase in flash drivers

2025-03-24 Thread Lwazi Dube
On Mon, 24 Mar 2025 at 04:50, Javier Casas Marin wrote: > In AT45DB161D chip, the Opcode 82H = Main Memory Page Program Through > Buffer *also performs a built-in erase.* > > From the datasheet, section 7.8: > "This operation is a combination of the Buffer Write and Buffer to Main > Memory Page P

Re: Double erase in flash drivers

2025-03-24 Thread Javier Casas Marin
In summary, I see two options: 1. If the built-in erase is not really necessary, instead of command 0x82 we can use commands 0x84 (Buffer 1 Write) followed by 0x88 (Buffer 1 to Main Memory Page Program without Built-In Erase), that seem to be common to all devices. 2. If there is any use case wher

Re: Can NSEC_PER_USEC in clock.h be changed to 1000L?

2025-03-24 Thread kr . git
Hello, thanks for the replies. I attached a gzipped patch and also posted it in clear below. It is based on 12.9 branch but should apply correctly to master branch as well. Hopefully someone with GitHub account finds the time. (Provided such a change indeed does not negatively affect other ar

Re: Can NSEC_PER_USEC in clock.h be changed to 1000L?

2025-03-24 Thread Sebastien Lorquet
Hello, I also dont have a github account (anymore), also for reasons. If you contribution is small enough (like a few lines) you can just show it on the mailing list and people with a github account may pick it up when they have time. Or send a git patch that would be easy to apply for peopl

Re: Double erase in flash drivers

2025-03-24 Thread Javier Casas Marin
In AT45DB161D chip, the Opcode 82H = Main Memory Page Program Through Buffer *also performs a built-in erase.* >From the datasheet, section 7.8: "This operation is a combination of the Buffer Write and Buffer to Main Memory Page Program with Built-in Erase operations." So the double erases are al