Almost all pages have been migrated from confluence to Documentation: https://github.com/apache/nuttx/issues/11127
Several pages have been intentionally omitted because the information in them was outdated or already present on other pages in the doc. Disabling confluence makes sense, we should have one official source of knowledge. If it's possible to redirect to the official doc page, it would be best pt., 28 sie 2026 o 18:10 Alan C. Assis <[email protected]> napisał(a): > Yes, maybe we should disable the confluence or even better: redirect it to > official page. > > I forgot to cite, but I think more people helped on the migration effort. > We need to double check to confirm if none page is missing. > > BR, > > Alan > > On Friday, August 28, 2026, Gregory Nutt <[email protected]> wrote: > >> Good news! Thanks! I am glad that years of effort and experience were >> no lost because of the bad decisions of a single contributor. >> >> So that means I can stop referencing all of the old documentation in >> responses. >> ------------------------------ >> *From:* Alan C. Assis <[email protected]> >> *Sent:* Friday, August 28, 2026 8:19 AM >> *To:* [email protected] <[email protected]> >> *Subject:* Re: Allwinner D1 / C906 NuttX bring-up, native Timer1 and >> benchmark results >> >> Hi Greg, >> >> I think that page was already migrated: >> https://nuttx.apache.org/docs/latest/implementation/short_time_delays.html >> >> I migrated a few pages and the Raiden created an Issue about missing >> pages to be migrated and he migrated the remaining (a lot of pages). >> >> Maybe there could be some missing page to be migrated, but I think all >> pages were already migrated. >> >> BR, >> >> Alan >> >> On Fri, Aug 28, 2026 at 12:03 PM Gregory Nutt <[email protected]> >> wrote: >> >> Is this the same issue as "Short Time Delays" >> https://cwiki.apache.org/confluence/spaces/NUTTX/pages/139629486/Short+Time+Delays >> >> >> There a LOT of information in these old documents — years of effort — >> that has been lost because there were never restored to the Documents >> directory where they removed by a cosmetic change. The new Documentation >> looks great but much was lost (and is now so old as to be untrustworthy). >> It would be great if these could be restored where they belong. >> >> >> ------------------------------ >> *From:* Alan C. Assis <[email protected]> >> *Sent:* Friday, August 28, 2026 5:19 AM >> *To:* [email protected] <[email protected]> >> *Subject:* Re: Allwinner D1 / C906 NuttX bring-up, native Timer1 and >> benchmark results >> >> Hi Lance, >> >> Nice port and nice test! Kudos! >> >> About the issue you found, maybe it is similar to the "+ 1" that makes >> usleep() and other time passages on NuttX add a +1 to the result. >> >> There is a 11 years old discussion about it: >> https://nuttx.yahoogroups.narkive.com/OEGj8wsV/delay-or-sleep-in-thread# >> >> Also, there is a documentation about this subject here: >> https://nuttx.apache.org/docs/latest/reference/os/time_clock.html >> >> Here is a quick AI-generated summary for those who don't want to read the >> source: >> >> [image: image.png] >> >> But I think your test is a little different and should be easily fixable >> (not sure). >> >> Yes, +1 for adding new features to this port! >> >> BR, >> >> Alan >> >> On Wed, Aug 26, 2026 at 11:57 PM Lance Harvie <[email protected]> >> wrote: >> >> Hi all, >> >> I’ve been working on an Allwinner D1 / XuanTie C906 using the Sipeed >> Lichee >> RV / 86 Panel and recently completed a local NuttX board port and a >> comparison against Linux and RT-Thread RT-Smart on the same hardware. >> >> I thought some of the bring-up findings might be useful to the NuttX >> community. >> >> The tested NuttX version was 13.0.1-RC0, initially brought up in FLAT >> S-mode under the existing OpenSBI/U-Boot environment. >> >> The first image reached NSH quite quickly, but then reset after roughly 20 >> seconds. The cause was inherited hardware state: U-Boot had left the >> Allwinner watchdog enabled, so NuttX booted successfully while carrying a >> guaranteed reset condition. >> >> After disabling the watchdog, timed sleeps still failed. >> >> OpenSBI advertised the SBI TIME extension and set_timer returned success, >> but the supervisor timer pending interrupt never appeared through STIP on >> the tested firmware path. >> >> I therefore moved the NuttX scheduler tick onto the native Allwinner D1 >> Timer1 peripheral through the PLIC. >> >> That exposed a second problem. >> >> With OSC24M as the clock source I originally programmed an interval of >> 24,000 for a nominal 1 ms scheduler tick. On the physical D1 this produced >> an effective period of 24,001 input clocks. >> >> The resulting error was only about 41.7 ppm, but over a ~20 second >> benchmark it accumulated to nearly 0.84 ms. >> >> Programming 23,999 produced the intended 24,000 input clocks per tick and >> reduced the measured clock-domain drift to essentially zero. >> >> After correcting the timer and tightening the measurement methodology, the >> loaded 1 ms periodic test produced: >> >> p50: 0.542 us >> p99: 0.583 us >> p99.9: 0.708 us >> max: 0.708 us >> missed: 0 / 20,000 >> >> The periodic task was FIFO120 and the continuous compute worker FIFO90 on >> the single C906 core. >> >> An important caveat is that this was a FLAT shared-address-space NuttX >> configuration. I am not presenting those numbers as equivalent to Linux >> protected-process overhead. >> >> I documented the watchdog diagnosis, SBI timer path, Timer1 >> implementation, >> phase-alignment methodology and failed intermediate tests here: >> >> GitHub: >> https://github.com/lanceharvie/allwinner-d1-os-benchmark >> >> Report: >> https://doi.org/10.5281/zenodo.22054539 >> >> I’d be interested in feedback from the NuttX maintainers on two things: >> >> 1. whether there is interest in taking the D1 board-port work further >> toward upstream quality, and >> 2. whether anyone has seen a similar D1/OpenSBI situation where SBI >> TIME >> accepts set_timer but STIP never becomes pending. >> >> Regards, >> Lance Harvie >> >>
