summaryrefslogtreecommitdiff
path: root/common_modules/module_lib/src/txm_module_application_request.c
diff options
context:
space:
mode:
authorFrédéric Desbiens <[email protected]>2026-08-16 08:42:53 -0400
committerGitHub <[email protected]>2026-08-16 08:42:53 -0400
commit0e7db2bf793e624ed50855baf2a2a0ad1d0d7cc9 (patch)
treef23bff18453ba8b6268555bcd430d3ddd7e9891a /common_modules/module_lib/src/txm_module_application_request.c
parent090f8edc56e40b1c5dde16d1c7f36f1428274324 (diff)
Stopped the generated Armv8-M readmes claiming a false origin date (#623)
Every Armv8-M port readme ends with 09-30-2020 Initial ThreadX 6.1 version for Cortex-M85 using GNU tools. with the core name substituted in by scripts/copy_armv8_m.sh. The date is the shared port's, so each core inherits it whatever its own history: Cortex-M85 was announced in 2022 and its readme claims a 2020 origin, and any core added later gets the same treatment the moment its name joins the generator's list. The rest of the history block is accurate, since it records changes to the shared files. Only the closing line asserts something per-core. Reword it to describe the Armv8-M port itself, and say where a given core's real starting point is. Regenerating updates the twelve readmes for cortex_m33, cortex_m52, cortex_m55 and cortex_m85 across the three toolchains. Cortex-M52 makes the point: it arrived in #519 and its readme immediately claimed a 2020 origin for a core announced in 2023. The ARMv7-M templates say "Initial ThreadX version 6.1.7 for Cortex-M", with no placeholder to substitute, so they make no per-core claim and are left alone. Assisted-by: Claude Code (Opus 5) <[email protected]>
Diffstat (limited to 'common_modules/module_lib/src/txm_module_application_request.c')
0 files changed, 0 insertions, 0 deletions