Re: usb modem "Can't setup transfer"

2015-11-11 Thread Hans Petter Selasky
On 11/11/15 04:37, Alfred Perlstein wrote: Hello, A friend gave me a usb modem recently. The model is: Multi-Tech Systems - Multi-Modem USB - MT5634ZBA The Linux driver info is here: ftp://ftp.multitech.com/usb/usb-linux2.txt When I plug this device into FreeBSD I get a ugen0 device. So I

Re: usb modem "Can't setup transfer"

2015-11-11 Thread Alfred Perlstein
On 11/11/15 12:36 AM, Hans Petter Selasky wrote: On 11/11/15 04:37, Alfred Perlstein wrote: Hello, A friend gave me a usb modem recently. The model is: Multi-Tech Systems - Multi-Modem USB - MT5634ZBA The Linux driver info is here: ftp://ftp.multitech.com/usb/usb-linux2.txt When I plug

Re: How to access a FTDI usb device with a custom vendor and product id's

2015-11-11 Thread Burton Sampley
I added a line to the table, but it seems to have failed since I used the VID# instead of the VID# name. Where are the VID names mapped to the VID#'s? Apparently, I know enough about coding to be dangerous. I'll do some more digging to try to fix my own error. Here's a diff of the original

Re: How to access a FTDI usb device with a custom vendor and product id's

2015-11-11 Thread Warner Losh
On Nov 10, 2015 9:53 AM, "Hans Petter Selasky" wrote: > > On 11/10/15 17:50, Ian Lepore wrote: >> >> On Tue, 2015-11-10 at 17:40 +0100, Hans Petter Selasky wrote: >>> >>> On 11/10/15 17:28, Burton Sampley wrote: SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56",

Re: How to access a FTDI usb device with a custom vendor and product id's

2015-11-11 Thread Ian Lepore
On Wed, 2015-11-11 at 16:28 -0500, Burton Sampley wrote: > I added a line to the table, but it seems to have failed since I used > the > VID# instead of the VID# name. Where are the VID names mapped to the > VID#'s? Apparently, I know enough about coding to be dangerous. > I'll do > some more

Re: How to access a FTDI usb device with a custom vendor and product id's

2015-11-11 Thread Burton Sampley
Ian, Thank you for your prompt reply. Looking at the usbdevs file, I found 0x2100, but there is no entry for 0x9e56, which is my device. So, I'm assuming that changing uftdi.c to the correct name for the VID will only solve part of my problem. I will further assume that I need to find the

Re: How to access a FTDI usb device with a custom vendor and product id's

2015-11-11 Thread Ian Lepore
On Wed, 2015-11-11 at 16:57 -0500, Burton Sampley wrote: > Ian, > > Thank you for your prompt reply. > > Looking at the usbdevs file, I found 0x2100, but there is no entry > for > 0x9e56, which is my device. So, I'm assuming that changing uftdi.c > to the > correct name for the VID will only