rt-thread.git/libcpu, branch copilot/fix-fpu-initialization-issueUnnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/rt-thread.git/atom/libcpu?h=copilot%2Ffix-fpu-initialization-issue2025-11-11T01:31:53Z[libcpu][cortex-a] Replace FPU init loop with rt_memset2025-11-11T01:31:53Zcopilot-swe-agent[bot]198982749+Copilot@users.noreply.github.com2025-11-11T01:31:53Zurn:sha1:06eae477b8b83774e32814cfa7bc87e65c53a439
Co-authored-by: BernardXiong <1241087+BernardXiong@users.noreply.github.com>
[libcpu][cortex-a] Improve FPU stack initialization implementation2025-11-11T01:24:47Zcopilot-swe-agent[bot]198982749+Copilot@users.noreply.github.com2025-11-11T01:24:47Zurn:sha1:4dc072c04c70f88fa7fcb3cd4558cb06e51b66c9
Co-authored-by: BernardXiong <1241087+BernardXiong@users.noreply.github.com>
[Components] Remove vbus component and realview-a8-vmm libcpu (#10863)2025-11-07T09:03:05ZCopilot198982749+Copilot@users.noreply.github.com2025-11-07T09:03:05Zurn:sha1:c631b3931764690466da11c2d793183f05262d5c
* Initial plan
* Remove vbus component and related code
Co-authored-by: BernardXiong <1241087+BernardXiong@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: BernardXiong <1241087+BernardXiong@users.noreply.github.com>[libcpu/arm/cortex-m33]: Fix incorrect CPU architecture in GCC context switch2025-11-02T08:23:31ZYucai Liuyucai.liu@sunseekerpower.cn2025-11-01T07:21:09Zurn:sha1:c91a7f46f576ea89271a29365b36fd3fd0265a01
The context_gcc.S file was incorrectly marked as cortex-m4 in both the
doxygen comment and .cpu directive, while the IAR and KEIL versions
correctly specify cortex-m33. This file uses ARMv8-M specific features
(PSPLIM register, TrustZone support) that are not available in Cortex-M4.
Changes:
- Update doxygen group from cortex-m4 to cortex-m33
- Change .cpu directive from cortex-m4 to cortex-m33
aarch64: document the CNTFRQ_EL02025-10-23T14:08:05ZYonggang Luoluoyonggang@gmail.com2025-10-21T07:53:14Zurn:sha1:0cf096e0645746aa18eacb01725a71373a574516
Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
[aarch64] Fix rt_aspace_init error when KERNEL_VADDR_START >= 0x800000002025-10-21T02:12:35ZSiwei Xuxusiwei1236@qq.com2025-10-20T12:32:40Zurn:sha1:1efceab0711f741c649730dd5c6c04ab96881badRemove unused rt_hw_set_gtimer_frq2025-10-13T13:44:36ZYonggang Luoluoyonggang@gmail.com2025-09-26T23:03:44Zurn:sha1:27e3460b889cf426bce896b77df951d03987e7b2bsp/w60x: fixes cppcheck: (#10781)2025-10-11T01:28:52ZYonggang Luoluoyonggang@gmail.com2025-10-11T01:28:52Zurn:sha1:5ae232b6d0752ab823b5d0a52ef0aa269fdb3aed
[cpp_check.py 80 INFO] bsp/w60x/drivers/drv_rtc.c:58:11: error: Syntax Error: AST broken, binary operator '&=' doesn't have two operands. [internalAstError]
[cpp_check.py 80 INFO] libcpu/arm/s3c24x0/rtc.c:34:12: error: Expression 'RTCCON|=RTCCON|=0x01' depends on order of evaluation of side effects [unknownEvaluationOrder]Remove rarely used rt_time_t2025-10-10T12:21:40ZYonggang Luoluoyonggang@gmail.com2025-09-27T00:20:12Zurn:sha1:62bc4ba774b9137e8ca5fbdd579ebfd09b6be033
next_delay should be rt_tick_t
Use time_t for RT_DEVICE_CTRL_RTC_GET_TIME
[CPU/AARCH64] 增加 libcpu/aarch64 KERNEL_ASPACE_START 配置 #107572025-10-10T03:02:28Zzhangyan103986797+messigogogo@users.noreply.github.com2025-10-10T03:02:28Zurn:sha1:cc72712173c610494bf32f8113a968c3ece5aee2
针对不同的 Aarch64 BSP 针对 KERNEL_VADDR_START 宏定义进行区分