Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Y2038 ARM #272

Closed
ngladitz opened this issue Apr 5, 2024 · 1 comment
Closed

Y2038 ARM #272

ngladitz opened this issue Apr 5, 2024 · 1 comment

Comments

@ngladitz
Copy link

ngladitz commented Apr 5, 2024

Hi! Not entirely sure this is the right place to bring this up.

I've got a sbRIO 9651 (32-bit ARM) that appears to be affected by the Year 2038 problem.

From what I understand Linux >= 5.1 and glibc >= 2.34 (better yet 2.35) would provide opt-in mitigations in form of a 64-bit time_t.

I've updated my system software installation to the currently most recent 2024Q1 (for which I've been unable to find corresponding tags / branches in this repository btw.) and find the presumably too old Linux 4.14.146-rt67 and glibc 2.24.

I also notice that the nilrt/master/sumo branch hasn't been touched in two years and the note in docs/README.kernel.md about only supporting Linux 4.14 and below on ARM.

Is the issue known / being worked on?
Is the ARM port still being worked on at all or has it perhaps moved elsewhere (I assume the updated system image releases have to be coming from somewhere)?

@jeminor
Copy link
Contributor

jeminor commented Apr 8, 2024

Hi @ngladitz and thanks for asking!

Not entirely sure this is the right place to bring this up.

This is a fine place to start, but from here I think your best option is to reach out to your local NI/Emerson sales and support team and have them raise a support issue. We would like to understand more about your use case, needs and timelines and that is typically the best pathway for us to gather that information comprehensively.

I will close this issue in favor of that communication pathway.

@jeminor jeminor closed this as completed Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants