-
Notifications
You must be signed in to change notification settings - Fork 514
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
Not buildable on i686 #550
Comments
The latest commit on which a 32 bit kernel module for kernel 6.1 is buildable is b92e9ce |
So, commit 9f51281 broke 32 bit |
Does this: diff --git a/drivers/media/v4l2-core/v4l2loopback.c b/drivers/media/v4l2-core/v4l2loopback.c
index 4659bdf7ebea..012bbcb11173 100644
--- a/drivers/media/v4l2-core/v4l2loopback.c
+++ b/drivers/media/v4l2-core/v4l2loopback.c
@@ -1541,7 +1541,7 @@ static int vidioc_reqbufs(struct file *file, void *fh,
{
struct v4l2_loopback_device *dev;
struct v4l2_loopback_opener *opener;
- int i;
+ int i, t;
MARK();
dev = v4l2loopback_getdevice(file);
@@ -1594,7 +1594,8 @@ static int vidioc_reqbufs(struct file *file, void *fh,
/* after we update dev->used_buffers, buffers in outbufs_list will
* correspond to dev->write_position + [0;b->count-1] range */
- i = dev->write_position % b->count;
+ t = dev->write_position;
+ i = do_div(t, b->count);
list_for_each_entry(pos, &dev->outbufs_list,
list_head) {
dev->bufpos2index[i % b->count] = fix the issue? |
No, it did not fix i686 builds https://abf.io/build_lists/4681832 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Thanks for the fix. |
Latest HEAD - 9ba7e29 - is buildable on x86_64 and aarch64, but is not on i686 (x86_32):
ERROR: modpost: "__moddi3" [/root/v4l2loopback/v4l2loopback.ko] undefined!
I do not see where
__moddi3
gets from.Actually nobody is going to use it on i686, so it is not a big problem.
Bigger log:
I'm not sure that the problem is in v4l2loopback.
The text was updated successfully, but these errors were encountered: