-
Notifications
You must be signed in to change notification settings - Fork 52
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
build failure: missing linux/vsc.h #13
Comments
How about moving ov01a10 and ov02c10 into ivsc-drivers? I didn't find there is a directly dependency to ipu6-drivers but ivsc. |
I added the vsc,h from the ivsc-drivers repo, which gets the build past that error. however, there is another error right after
|
At this moment, the vsc driver needs to be built as part of the kernel so that the sensor drivers can link against it. |
I'm afraid that's not gonna happen any more as Intel has no interest in upstreaming this any time soon. It has to be a standaline dkms. That's all. So this, missing |
And please note we are expecting your commitment into CI tests for both ipu6-drivers and ivsc-drivers. |
what the CI tests will be? Can you please add some extra commands to clone/wget the missing header files from https://github.com/torvalds/linux/tree/master/drivers/misc/mei after git clone ivsc driver code? |
@vicamo if just copying these missing header files into ivsc driver repo, we have to take much effort to maintain these header files which are not developed by us as kernel upgrades. |
Then you probably now understand how downstream kernel vendors struggled to maintain your ivsc driver between kernel versions. Again, we're expecting them being built as dkms. |
please note copying these header files into ivsc driver repo may break other modules if vendors still follow the current building way. Is that ok for you to make another branch for dkms? |
See intel/ivsc-driver#13. Next is to move the two affected sensors here into ivsc either in your repo or in our debian package.
No. |
Ok, but actually I'm trying to take out the structure and function declaration needed into a separate header file to reduce the maintain effort. Anyway thanks for your PR. |
Is there a good way to get the modpost error fixed for those of us using the DKMS build (in my case, using Debian sid's 5.18.0-2-amd64)? I've built and installed the ivsc-driver already with DKMS. |
Did anyone get past these MODPOST errors? Trying to build this driver on Fedora 36. |
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1972109 |
Thanks! I cloned the repos, applied the patches in |
@zebra-ok did you just install the dkms modules for those both projects or anything else? Building and installing worked well, but a camera device is not showing up for me. |
@zebra-ok I'm also trying to get this working on Fedora36, but am struggling to make any real progress. The patches don't apply cleanly for me, and I can't get this repo or the 'hal' repo to build successfully currently. Any chance you could provide more details on what order you built and patched everything to get the camera working? |
so there's no way for a DKMS module to depend on another DKMS module? Would an approach based on I'm currently writing an Arch Linux |
Just for the record, the ChromiumOS Linux kernel, has the driver integrated in some of their Linux version branches – at least up to 5.15 – for example CHROMIUM: media: intel-ipu6: copy IPU6 driver from v5.4 branch and follow-up change-sets/commits. |
@Thesola10 have you managed building and getting the camera to run manually, if so with what steps? |
This comment was marked as outdated.
This comment was marked as outdated.
Update: Got a pure-DKMS version of the whole ipu6 driver stack working over on AUR: The resulting V4L2 device can't be used as-is, (Of course, I have built an AUR package for that too: |
Nice. What Linux versions are supported? |
Likely everything that this repo supports, as long as |
The text was updated successfully, but these errors were encountered: