fix(am335x/am437x): Remove RTOS and RT-Linux support #625
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jeevantelukula
requested review from
StaticRocket,
VeeruPrudhvi,
cshilwant,
gehariprasath,
praneethbajjuri and
uditkumarti
as code owners
github-actions
bot
assigned
devarsht,
gehariprasath,
praneethbajjuri,
r-vignesh and
uditkumarti
|
New unreachable files found with check_files.py: |
praneethbajjuri
requested changes
Feb 4, 2026
| @@ -126,8 +126,6 @@ linux/How_to_Guides/Target/How_to_add_a_JVM | |||
| linux/How_to_Guides/Target/Update_U-Boot_Environment_Variables_stored_in_SPI_Flash_from_Linux | |||
| linux/How_to_Guides/Target/How_to_Change_dtb_File | |||
| linux/How_to_Guides/Target/How_to_fix_y2k38 | |||
Collaborator
There was a problem hiding this comment.
might want to remove this as well from toc?
linux/How_to_Guides/Target/How_to_fix_y2k38.
Also , split all y2k38 removal as separate patch
Collaborator
Author
There was a problem hiding this comment.
I'd say lets have this section in this release highlighting the resolution and can be dropped in the future releases.
Collaborator
Audit this cleanup warning as well |
Member
|
FYI, |
RTOS and RT-Linux are not supported for AM335x and AM437x in this release. Remove all related documentation, hardware setup guides, TOC entries, and build instructions. Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com>
EVMK2H is outdated and hence remove all its references. Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com>
Since the y2k38 issue is resolved in scarthgap, highlight the resolution in this release. Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com>
jeevantelukula
force-pushed
the
master
branch
from
af953a3 to
e9cbfea
Compare
cshilwant
reviewed
Feb 9, 2026
| https://software-dl.ti.com/cicd-report/linux/index.html?section=platform&platform=am437x | ||
|
|
||
| The above images are based on the 6.6 Kernel and Scarthgap filesystem, and thus has the Y2K38 issue fixed. | ||
| TI's 32-bit platforms now use OE-core Scarthgap, which includes the necessary updates to data structures and functions |
Member
There was a problem hiding this comment.
Better to highlight how Yocto / OpemEmbedded ensures distributions the same.
Checkout https://wiki.st.com/stm32mpu/wiki/How_to_prevent_the_year_2038_bug#Compile_all_the_codes_in_Yocto_with_required_defines
Member
There was a problem hiding this comment.
I think it's better to reword,
Fix --> Prevent
As there’s no way to conclusively prove that any given system is Y2038-safe.
| https://software-dl.ti.com/cicd-report/linux/index.html?section=platform&platform=am437x | ||
|
|
||
| The above images are based on the 6.6 Kernel and Scarthgap filesystem, and thus has the Y2K38 issue fixed. | ||
| TI's 32-bit platforms now use OE-core Scarthgap, which includes the necessary updates to data structures and functions |
Member
There was a problem hiding this comment.
Better to highlight how Yocto / OpemEmbedded ensures distributions the same.
Checkout https://wiki.st.com/stm32mpu/wiki/How_to_prevent_the_year_2038_bug#Compile_all_the_codes_in_Yocto_with_required_defines
| To build a Y2K38-friendly image on the 6.6 Kernel and Scarthgap filesystem baseline, follow the "Build Instructions" | ||
| section present in the above link. | ||
| While the SDK images are Y2K38-friendly, it must be ensured that any code introduced from other sources | ||
| is also Y2K38-friendly. Any code that is not Y2K38-compliant will break the Y2K38-compatibility of the filesystem. |
Member
There was a problem hiding this comment.
This can be expanded to showcase the 'how to ensure" aspect
https://wiki.st.com/stm32mpu/wiki/How_to_prevent_the_year_2038_bug#GNU_C_library_required_version
| While the SDK images are Y2K38-friendly, it must be ensured that any code introduced from other sources | ||
| is also Y2K38-friendly. Any code that is not Y2K38-compliant will break the Y2K38-compatibility of the filesystem. | ||
| Thus it is important to be intentional about writing Y2K38-friendly code, and to test this code to ensure that the | ||
| final image remains Y2K38-compliant. |
Member
There was a problem hiding this comment.
You can also add a section How to check if your system is Y2k38 friendly
And provide a command which sets date beyond 2038 and shows the behaviour of the system in safe v/s non safe case
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RTOS and RT-Linux are not supported for AM335x and AM437x in this release. Remove all related documentation, hardware setup guides, TOC entries, and build instructions.
Also update Y2K38 docs to reflect resolution in Scarthgap.