Timeline for i2c driver linux, where is .ko file, recompile single driver and enable
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2023 at 7:14 | comment | added | sawdust | You persist in only providing tiny summations that bolster your confusing conclusions. Instead of scrutinizing the boot log line by line, you take shortcuts using grep. Where is the raw data for others to review and determine if your assertions are correct? If you could analyze this raw data (e.g. boot logs, DT, .config) correctly, then you probably would not be asking for help. Vote to close for lack of detail. | |
| Aug 24, 2023 at 19:46 | comment | added | nx4n | @sawdust, there is only i2c_dev: i2c /dev entries driver in the dmesg output, and i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 after i2cdetect -y 0. I don't have new kernel. There is nothing with mv64xxx or MV64XXX substrings in the boot log | |
| Aug 24, 2023 at 18:47 | review | Close votes | |||
| Sep 9, 2023 at 21:49 | |||||
| Aug 18, 2023 at 7:23 | answer | added | grawity_u1686 | timeline score: 1 | |
| Aug 18, 2023 at 7:21 | comment | added | sawdust | Did you review the boot log of the original kernel? What messages (if any) did the original i2c_mv64xxx driver generate? Where in the boot sequence do they occur? Did you review the boot log of the new kernel? What messages (if any) did the modified i2c_mv64xxx driver generate? | |
| Aug 18, 2023 at 6:53 | history | edited | nx4n | CC BY-SA 4.0 |
added 601 characters in body
|
| Aug 18, 2023 at 6:41 | comment | added | nx4n | And about "careless with names": I tried to find / -type f -name "mv64xxx" before compiling module and result was empty => also there is not i2c-mv64xxx.ko and other files in my fs | |
| Aug 18, 2023 at 6:33 | comment | added | nx4n | @sawdust new function void return, old int and return 0, bruh. I did depmode and then modprobe i2c-mv64xxx, no errors, nothing is going on. lsmod | grep i2c : empty, dmesg | grep mv64 : empty, dmesg | grep i2c : i2c_dev: i2c /dev entries driver, BUT, it was already before I recompile module. May be old module dont give me load new module? | |
| Aug 18, 2023 at 6:27 | comment | added | nx4n | @sawdust, I did it, I recompiled new module! There was several easy changes, one function with another return type and one struct with one another name of field that takes this function pointer. I have new i2c-mv64xxx.ko file and other files within directory with this module. But how to enable him now? I try modprobe, but no this driver in lsmod and after modprobe no errors, just new prompt :( | |
| Aug 17, 2023 at 21:34 | comment | added | sawdust |
"I can't figure out where the mv64xxx.ko file is located" -- That's because you're careless with names. The Kconfig entry states: This driver (i2c_mv64xxx.c) can also be built as a module. If so, the module will be called i2c-mv64xxx. "I want to replace my current mv64xxx driver on linux 5.17 with the mv64xxx driver from linux >= 6.4." -- Not feasible. The internal interfaces of the kernel can change between kernel versions. Instead you would have to back-port the salient patch.
|
|
| S Aug 17, 2023 at 11:42 | review | First questions | |||
| Aug 17, 2023 at 11:46 | |||||
| S Aug 17, 2023 at 11:42 | history | asked | nx4n | CC BY-SA 4.0 |