Sebastian Huber created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1454
Project:Branches: sebhub/rtems:up/x86_64-counter to rtems/rtos/rtems:main Author: Sebastian Huber ## Summary Issue #5729: The CPU counter counts calls and the frequency truncates Two commits. The first gives the timecounter the frequency as it is. The second moves the measurement of the time stamp counter frequency into the CPU counter support, where it runs against channel 2 of the PIT in the CPU counter step of the system initialization, and reads that counter as the CPU counter. A system without a clock driver gets the counter this way as well. The two are independent and the first stands on its own. **BSP** `x86_64/amd64` ยท **Simulator** Qemu ## AI Details <!-- Make sure you have read our statement at https://www.rtems.org/generative-ai/ --> ### Prompt used None as a single prompt. The work was done in an interactive Claude Code session on the RTEMS tree. The task was to run the test suites of the simulator BSPs, diagnose every failure and fix the cause. Each change was directed and reviewed. ### AI model used Claude Opus 5 (claude-opus-5), through Claude Code. ### How AI was used for the contribution - [ ] Formatting - [ ] Test creation. - [x] Code comments. - [ ] The entire contribution was generated using AI - [ ] AI code completion such as Copilot in VSCode. The diagnosis and the implementation were produced in that session under my direction, and the commit messages were drafted there. ### Access I have not used a product which claims copyright in its output, and I have legitimate access to the one I used. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1454 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-ce2f53koai05u5g35spxlswbt-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
