No, but the workaround I used is to build and install your own kernel, and use the same toolchain to compile your module. That way their symbol version will match.As far as I understand, were you able to solve the problem?
Nope. And I don't think it would be easy -- the missing piece of knowledge is on raspberry pi kernel developers side -- how they build the kernels, what's their environment, etc. I don't have any visibility into that.And in general, have you been able to figure out what is going on?
The other way would be to figure out how the symver CRCs are computed exactly, and then try to "invert the hash" get what would the input there be to get these values. Also, inspecting debug info and assembly (functions signatures, structure layouts, etc.) could help.
I'm not up to investigation that deep at this moment
.Yeah, I'm new to this modules thing too.I'm just starting to learn about drivers, but I've been having this problem for three weeks now.
Statistics: Posted by provod — Fri Apr 05, 2024 7:12 pm