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

Rename ipu6 .ko files to avoid conflict with upstream ipu6 isys support #243

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jwrdegoede
Copy link
Contributor

Now that IPU6 isys support has landed upstream, using an auxbus approach rather then the custom ipu6-bus, there is a conflict between the mainline intel-ipu6* kernel modules and the out of tree ipu6-drivers intel-ipu6* kernel modules.

Rename the out of tree ipu6 modules to icamera-ipu6* so that both can be installed together and the user can easily switch by blacklisting one of the 2 sets of modules.

Cc: @vicamo @smallorange (FYI)

Now that IPU6 isys support has landed upstream, using an auxbus approach
rather then the custom ipu6-bus, there is a conflict between the mainline
intel-ipu6* kernel modules and the out of tree ipu6-drivers intel-ipu6*
kernel modules.

Rename the out of tree ipu6 modules to icamera-ipu6* so that both can be
installed together and the user can easily switch by blacklisting one of
the 2 sets of modules.

Signed-off-by: Hans de Goede <[email protected]>
@vicamo
Copy link
Contributor

vicamo commented Jun 17, 2024

That's probably not my call, but while Ubuntu/Debian are using dkms to handle out-of-tree kernel modules, they're installed to a different path, and the one from dkms will have higher priority. We don't have this problem.

@jwrdegoede
Copy link
Contributor Author

That's probably not my call, but while Ubuntu/Debian are using dkms to handle out-of-tree kernel modules, they're installed to a different path, and the one from dkms will have higher priority. We don't have this problem.

With 6.10 there also is IPU6 support in the mainline kernel, the idea is to easily allow switching between the 2 driver sets by blacklisting one or the other in a /etc/modprobe.d/ dropin file. Using /lib/modules/$kver/updates as dkms does will cause the out of tree driver to always get loaded and thus does not allow easily switching back to the mainline driver after the out of tree driver has been installed.

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

Successfully merging this pull request may close these issues.

2 participants