[prev in list] [next in list] [prev in thread] [next in thread]
List: libusb-devel
Subject: Re: [libusb] In Windows 10, Isochronous OUT transfers not returning actual length in callback
From: Krishna Chaitanya Chunduru <krishnachaitanya.chunduru () soctronics ! com>
Date: 2019-01-08 3:15:18
Message-ID: 18985492.319.1546916590169.JavaMail.kchundru () HYKCHUNDRU
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
No, number of packets is '1'.
For isochronous IN also it is showing as 0 only, but we are getting correct length.
Thanks & Regards,
Chaitanya.
----- Original Message -----
From: "Tim Roberts" <timr@probo.com>
To: "Libusb Mailing List" <libusb-devel@lists.sourceforge.net>
Sent: Tuesday, January 8, 2019 12:28:38 AM
Subject: Re: [libusb] In Windows 10, Isochronous OUT transfers not returning actual \
length in callback function, but works fine in windows 7
Krishna Chaitanya Chunduru wrote:
> I have captured trace on host side using microsoft message analyzer.
> In that I can see lengthCompleted field having the correct value but
> this is not populated in the libusb transfer structure.
> This is only observed only windows 10 only.
> I am attaching the screenshot of microsoft message analyzer.
I notice that NumberOfPackets is 0. Are you specifying num_iso_packets
in your packet array?
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
_______________________________________________
libusb-devel mailing list
libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel
[Attachment #5 (text/html)]
<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div \
style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: \
#000000'>No, number of packets is '1'. <br>For isochronous IN also it is \
showing as 0 only, but we are getting correct length. <br><br><div><span \
name="x"></span><span style="color: rgb(77, 77, 77);"><span style="color: rgb(51, 51, \
51);"></span></span><span style="color: rgb(51, 51, 51);">Thanks & \
Regards,<br>Chaitanya.<br></span><span style="font-size: 9pt; font-family: \
"Arial",sans-serif; color: rgb(89, 89, 89);"></span><span \
name="x"></span><br></div><hr id="zwchr"><div style="color: rgb(0, 0, 0); \
font-weight: normal; font-style: normal; text-decoration: none; font-family: \
Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Tim Roberts" \
<timr@probo.com><br><b>To: </b>"Libusb Mailing List" \
<libusb-devel@lists.sourceforge.net><br><b>Sent: </b>Tuesday, January 8, 2019 \
12:28:38 AM<br><b>Subject: </b>Re: [libusb] In Windows 10, Isochronous OUT transfers \
not returning actual length in callback function, but works fine in windows \
7<br><br>Krishna Chaitanya Chunduru wrote:<br>> I have captured trace on host side \
using microsoft message analyzer. <br>> In that I can see lengthCompleted field \
having the correct value but <br>> this is not populated in the libusb transfer \
structure.<br>> This is only observed only windows 10 only.<br>> I am attaching \
the screenshot of microsoft message analyzer.<br><br><br>I notice that \
NumberOfPackets is 0. Are you specifying num_iso_packets <br>in your packet \
array?<br><br>-- <br>Tim Roberts, timr@probo.com<br>Providenza & Boekelheide, \
Inc.<br><br><br><br><br>_______________________________________________<br>libusb-devel \
mailing list<br>libusb-devel@lists.sourceforge.net<br>https://lists.sourceforge.net/lists/listinfo/libusb-devel<br></div><br></div></body></html>
_______________________________________________
libusb-devel mailing list
libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic