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

NVS compilation error, kirkstone #1628

Closed
intera91 opened this issue Jul 18, 2024 · 4 comments
Closed

NVS compilation error, kirkstone #1628

intera91 opened this issue Jul 18, 2024 · 4 comments

Comments

@intera91
Copy link

intera91 commented Jul 18, 2024

/kernel-source/nvidia/drivers/misc/nvs/nvs_timestamp.c:25:16: error: implicit d$
claration of function 'timespec_to_ns'; did you mean 'timespec64_to_ns'? [-Werror=implicit-function-declaration]
|    25 |         return timespec_to_ns(&ts);
|       |                ^~~~~~~~~~~~~~
|       |                timespec64_to_ns
| cc1: all warnings being treated as errors
@ichergui
Copy link
Member

Hi @intera91
Could you please share the steps you followed until having the issue ?

@intera91
Copy link
Author

intera91 commented Jul 18, 2024

Just a simple bitbake virtual/kernel after enabling CONFIG_NVS in the kernel as we have an ICM20689 in our production board that is connected to SPI

@ichergui
Copy link
Member

I will take a look and will get back to you

@madisongh
Copy link
Member

madisongh commented Jul 18, 2024

It would help to know which branch you're using, but I'm guessing it's one of the L4T R35.x-based branches with the 5.10 kernel...

The old 32-bit timespec structure, and related functions, were removed in (I think) the 5.6 kernel - part of fixing the Y2038 problem in the kernel. I suspect that NVIDIA just hasn't updated that driver for 5.10, since it's not part of the stock kernel configuration for L4T. Try patching the driver to use timespec64_to_ns instead; since we're a 64-bit architecture, timespecs even pre-5.6 should have been mapped into timespec64s anyway.

ETA: I just noticed that you do mention "kirkstone" in the title, so my guess was right.

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

3 participants