-
Notifications
You must be signed in to change notification settings - Fork 35
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
RPi 4 test result #18
Comments
Could you try this: int usb_raw_ep_read(int fd, struct usb_raw_ep_io *io) {
int rv = ioctl(fd, USB_RAW_IOCTL_EP_READ, io);
if (rv == -EINPROGRESS) {
// Ignore failures caused by the test that halts endpoints.
return rv;
}
if (rv < 0) {
perror("ioctl(USB_RAW_IOCTL_EP_READ)");
exit(EXIT_FAILURE);
}
return rv;
} And the same change for |
Hi, Seems that if (errno == EINPROGRESS) {
// Ignore failures caused by the test that halts endpoints.
return rv;
} If this looks good to you, then I will send a PR for RPi 4 testing result with this code change |
Ah, |
FTR, if you end up testing even more different hardware, there's a patch from Jahn Horn, which might be required. |
I just send a PR #19 , let me know if I did anything wrong
Ok, noted |
Hi
I tested
raw-gadget
with RPi 4, and when the test case 13(bulk, ep halt set/clear) was executed, there will be an error, sometimes it isioctl(USB_RAW_IOCTL_EP_WRITE): Operation now in progress
, and sometimes it isioctl(USB_RAW_IOCTL_EP_READ): Operation now in progress
seems that there is something interrupting the
down_interruptible()
function in line 94 ofraw-gadget.c
, which cause it return-EINTR
then I edited the
gadget.c
like this, simply just retry if error occured.RPi 4 is able to pass the
run_test.py
after this modificationThe question is: should I just add the test result for RPi 4 that tested with the above modification? or should I also modify the ioctl mechanism in
gadget.c
like the above?The text was updated successfully, but these errors were encountered: