Dear kernel list,
I bought a DVI to VGA adapter[0] hoping to make it work with the
modules udl or udlfb. The program lsusb does recognize it as a
DisplayLink:
//// lsmod output:
Bus 002 Device 004: ID 17e9:4300 DisplayLink
But, it does not matter what of the two modules I have loaded it
seems the kernel does not recognize it
# modprobe udl
//// plugging
# dmesg|tail -3
[ 5500.731973] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
[ 5500.747190] usbip-host 2-1:1.0: 2-1 is not in match_busid table... skip!
[ 5500.747760] usbip-host 2-1:1.1: 2-1 is not in match_busid table... skip!
//// unplugging
# rmmod udl
# modprobe udlfb
//// plugging
# dmesg|tail -4
[ 5544.168599] usb 2-1: USB disconnect, device number 5
[ 5560.144758] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[ 5560.160033] usbip-host 2-1:1.0: 2-1 is not in match_busid table... skip!
[ 5560.160585] usbip-host 2-1:1.1: 2-1 is not in match_busid table... skip!
I tried seeking on the Internet, but I could not find anything about
this 17e9:4300 model. So I ask, it will be supported? It is already
supported somewhat? Can I help? I have no experience in kernel
programming; but asking is legit I guess.
Please if you answer put my address [email protected] in
CC as I did not register to the mailing list scared by the huge volume.
Yours sincerely,
Paolo Bolzoni
[0] http://www.amazon.co.uk/exec/obidos/ASIN/B0086359SG/ref=ox_ya_os_product
Dear Paolo Bolzini,
On Mon, Jul 22, 2013 at 2:58 PM, Paolo Bolzoni
<[email protected]> wrote:
> Dear kernel list,
> I bought a DVI to VGA adapter[0] hoping to make it work with the
> modules udl or udlfb. The program lsusb does recognize it as a
> DisplayLink:
>
> //// lsmod output:
> Bus 002 Device 004: ID 17e9:4300 DisplayLink
>
> But, it does not matter what of the two modules I have loaded it
> seems the kernel does not recognize it
Matching is done by VID = 0x17e9 which seem match but then by
bInterfaceClass = 0xff, bInterfaceSubClass = 0x00 and bInterfaceProtocol = 0x00.
Can you please post lsusb -v to check what are other parameters for your device.
>
> # modprobe udl
> //// plugging
> # dmesg|tail -3
> [ 5500.731973] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
> [ 5500.747190] usbip-host 2-1:1.0: 2-1 is not in match_busid table... skip!
> [ 5500.747760] usbip-host 2-1:1.1: 2-1 is not in match_busid table... skip!
> //// unplugging
> # rmmod udl
> # modprobe udlfb
> //// plugging
> # dmesg|tail -4
> [ 5544.168599] usb 2-1: USB disconnect, device number 5
> [ 5560.144758] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
> [ 5560.160033] usbip-host 2-1:1.0: 2-1 is not in match_busid table... skip!
> [ 5560.160585] usbip-host 2-1:1.1: 2-1 is not in match_busid table... skip!
>
> I tried seeking on the Internet, but I could not find anything about
> this 17e9:4300 model. So I ask, it will be supported? It is already
> supported somewhat? Can I help? I have no experience in kernel
> programming; but asking is legit I guess.
>
> Please if you answer put my address [email protected] in
> CC as I did not register to the mailing list scared by the huge volume.
>
> Yours sincerely,
> Paolo Bolzoni
>
>
> [0] http://www.amazon.co.uk/exec/obidos/ASIN/B0086359SG/ref=ox_ya_os_product
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Regards,
marek
--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
On Mon, Jul 22, 2013 at 10:07 PM, Belisko Marek <[email protected]> wrote:
>> But, it does not matter what of the two modules I have loaded it
>> seems the kernel does not recognize it
> Matching is done by VID = 0x17e9 which seem match but then by
> bInterfaceClass = 0xff, bInterfaceSubClass = 0x00 and bInterfaceProtocol = 0x00.
> Can you please post lsusb -v to check what are other parameters for your device.
Sure thing, I appended the output at the end of the email because it
is a little long.
Please if you answer put my address [email protected] in
CC as I did not register to the mailing list.
Your sincerely,
Paolo
Here is the lsusb -v output about my DisplayLink:
Bus 003 Device 002: ID 17e9:4300 DisplayLink
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 9
idVendor 0x17e9 DisplayLink
idProduct 0x4300
bcdDevice 2.36
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 103
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 126mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 3
iInterface 0
** UNRECOGNIZED: 0c 5f 01 00 0a 00 04 04 01 00 04 00
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 5
bMaxBurst 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
Device Firmware Upgrade Interface Descriptor:
bLength 9
bDescriptorType 33
bmAttributes 1
Will Not Detach
Manifestation Intolerant
Upload Unsupported
Download Supported
wDetachTimeout 200 milliseconds
wTransferSize 1024 bytes
bcdDFUVersion 1.01
** UNRECOGNIZED: 10 40 06 01 09 01 01 03 45 6c 6c 61 44 6f 63 6b
On Tue, Jul 23, 2013 at 10:15 AM, Paolo Bolzoni
<[email protected]> wrote:
> On Mon, Jul 22, 2013 at 10:07 PM, Belisko Marek <[email protected]> wrote:
>>> But, it does not matter what of the two modules I have loaded it
>>> seems the kernel does not recognize it
>> Matching is done by VID = 0x17e9 which seem match but then by
>> bInterfaceClass = 0xff, bInterfaceSubClass = 0x00 and bInterfaceProtocol = 0x00.
>> Can you please post lsusb -v to check what are other parameters for your device.
> Sure thing, I appended the output at the end of the email because it
> is a little long.
>
> Please if you answer put my address [email protected] in
> CC as I did not register to the mailing list.
>
> Your sincerely,
> Paolo
>
>
> Here is the lsusb -v output about my DisplayLink:
Can you please try following patch:
diff --git a/drivers/video/udlfb.c b/drivers/video/udlfb.c
index d2e5bc3..a9c96f4 100644
--- a/drivers/video/udlfb.c
+++ b/drivers/video/udlfb.c
@@ -64,6 +64,16 @@ static struct usb_device_id id_table[] = {
USB_DEVICE_ID_MATCH_INT_SUBCLASS |
USB_DEVICE_ID_MATCH_INT_PROTOCOL,
},
+ {.idVendor = 0x17e9,
+ .bInterfaceClass = 0xff,
+ .bInterfaceSubClass = 0x00,
+ .bInterfaceProtocol = 0x03,
+ .match_flags = USB_DEVICE_ID_MATCH_VENDOR |
+ USB_DEVICE_ID_MATCH_INT_CLASS |
+ USB_DEVICE_ID_MATCH_INT_SUBCLASS |
+ USB_DEVICE_ID_MATCH_INT_PROTOCOL,
+
+ },
{},
};
MODULE_DEVICE_TABLE(usb, id_table);
>
> Bus 003 Device 002: ID 17e9:4300 DisplayLink
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 3.00
> bDeviceClass 239 Miscellaneous Device
> bDeviceSubClass 2 ?
> bDeviceProtocol 1 Interface Association
> bMaxPacketSize0 9
> idVendor 0x17e9 DisplayLink
> idProduct 0x4300
> bcdDevice 2.36
> iManufacturer 1
> iProduct 2
> iSerial 3
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 103
> bNumInterfaces 2
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 126mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 3
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 0
> bInterfaceProtocol 3
> iInterface 0
> ** UNRECOGNIZED: 0c 5f 01 00 0a 00 04 04 01 00 04 00
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x02 EP 2 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0400 1x 1024 bytes
> bInterval 0
> bMaxBurst 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x84 EP 4 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0400 1x 1024 bytes
> bInterval 0
> bMaxBurst 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x85 EP 5 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0008 1x 8 bytes
> bInterval 5
> bMaxBurst 0
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 1
> bAlternateSetting 0
> bNumEndpoints 0
> bInterfaceClass 254 Application Specific Interface
> bInterfaceSubClass 1 Device Firmware Update
> bInterfaceProtocol 1
> iInterface 0
>
> Device Firmware Upgrade Interface Descriptor:
> bLength 9
> bDescriptorType 33
> bmAttributes 1
> Will Not Detach
> Manifestation Intolerant
> Upload Unsupported
> Download Supported
> wDetachTimeout 200 milliseconds
> wTransferSize 1024 bytes
> bcdDFUVersion 1.01
> ** UNRECOGNIZED: 10 40 06 01 09 01 01 03 45 6c 6c 61 44 6f 63 6b
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
marek
--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer
Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
On Mon, Jul 22, 2013 at 10:58 PM, Paolo Bolzoni
<[email protected]> wrote:
> Dear kernel list,
> I bought a DVI to VGA adapter[0] hoping to make it work with the
> modules udl or udlfb. The program lsusb does recognize it as a
> DisplayLink:
USB3 devices are competely different and not supported.
Dave.
On Tue, Jul 23, 2013 at 10:47 AM, Dave Airlie <[email protected]> wrote:
> On Mon, Jul 22, 2013 at 10:58 PM, Paolo Bolzoni
> <[email protected]> wrote:
>> Dear kernel list,
>> I bought a DVI to VGA adapter[0] hoping to make it work with the
>> modules udl or udlfb. The program lsusb does recognize it as a
>> DisplayLink:
>
> USB3 devices are competely different and not supported.
So it is not even worth to try the patch?
Please if you answer put my address [email protected] in
CC as I did not register to the mailing list.
Paolo