From: dave p. <dpe...@gm...> - 2022-08-03 19:34:59
|
Hi Jakub, The suspicious entry is: bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 A genuine card sets the poll interval for the interrupt endpoint to 2 ms: bInterval 2 We have seen this before a couple of times. For the fake cards in the syslog you would see a message from the USB core similar to this: usb 2-1.1: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 7 We have not figured out how the adapter is initialised in windows. For that a trace of the initialisation with usbmon would be required. As you are running windows in qemu this should be relatively easy to do, cheers, -Dave On Wed, 3 Aug 2022 at 09:13, Jakub Ladman <la...@vo...> wrote: > > Hi Jakub, > > One way to check is to look at: the output of the syslog lines with > "gpib" in them and the output of "lsusb -d 3923:", with the adapter > plugged in. > > cheers, > > -dave > > > Hello > > First of all, I wrote that the device is working with windows, but the > part I omitted is - windows is running in qemu on the same machine, > where I'm testing the linux-gpib. > > I can't show you the syslog output, because I have now installed the > closed source driver and appropriate software from National Instruments > (which I don't want to use in the end, but I use it now as a sanity > check only). > > The lsusb output is: > $ lsusb -d 3923: -v > > Bus 001 Device 020: ID 3923:709b National Instruments Corp. GPIB-USB-HS > Couldn't open device, some information will be missing > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 > idVendor 0x3923 National Instruments Corp. > idProduct 0x709b GPIB-USB-HS > bcdDevice 1.01 > iManufacturer 1 National Instruments > iProduct 2 GPIB-USB-HS > iSerial 3 019BF124 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 0x0035 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0x80 > (Bus Powered) > MaxPower 500mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 5 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x06 EP 6 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x84 EP 4 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x88 EP 8 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > > If you see something strange here, please let me know. > > Thank you. > > Jakub Ladman > > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > |