Date: Wed, 11 Nov 2015 15:04:15 -0700 From: Ian Lepore <ian@freebsd.org> To: Burton Sampley <bsmply@gmail.com> Cc: Hans Petter Selasky <hps@selasky.org>, freebsd-usb@freebsd.org Subject: Re: How to access a FTDI usb device with a custom vendor and product id's Message-ID: <1447279455.91061.24.camel@freebsd.org> In-Reply-To: <CANV5k3omAmBEy00Ny2uhc_NaqnDKbY1knNM8F_wWn2M-o7PHXQ@mail.gmail.com> References: <CANV5k3rW62rGoXKD4m5meegEJ04T4b_v=QGCqBV5wuGxZjzCbg@mail.gmail.com> <56421DFD.6070503@selasky.org> <CANV5k3oRPP_-_SBz2fih0tA12BzoO9Ua%2BAfJGaE_CCNE3JzpHQ@mail.gmail.com> <564222D8.6020900@selasky.org> <CANV5k3qzn1UU=qvczGXUr3HQhxf0H8emKSV2XBDD%2B%2BfDr1yfjg@mail.gmail.com> <56422764.4040307@selasky.org> <CANV5k3pCx%2B3za1aPi=u5o36EvicgMgODL=eiTz-_s=nZLqbbAQ@mail.gmail.com> <1447277889.91061.22.camel@freebsd.org> <CANV5k3omAmBEy00Ny2uhc_NaqnDKbY1knNM8F_wWn2M-o7PHXQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 solve part of my problem. I will > further assume that I need to find the correct/proper entry for > usbdevs as > well. Is this a correct assumption? If so, then how/where can I > find the > proper entry for usbdevs? > > Here's the 2 closest entries: > > /* RT system products */ > product RTSYSTEMS CT29B 0x9e54 FTDI compatible adapter > product RTSYSTEMS SERIAL_VX7 0x9e52 FTDI compatible > adapter > > For me, what appears to be the last piece of the puzzle is to find > the > correct name to place in the 3rd field. Based on the following: > > $ /usr/local/bin/sudo /usr/sbin/usbconfig -d ugen2.3 dump_device_desc > ugen2.3: <CT-62B Radio Cable RT Systems> at usbus2, cfg=0 md=HOST > spd=FULL > (12Mbps) pwr=ON (90mA) > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 <Probed by interface class> > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0008 > idVendor = 0x2100 > idProduct = 0x9e56 > bcdDevice = 0x0600 > iManufacturer = 0x0001 <RT Systems> > iProduct = 0x0002 <CT-62B Radio Cable> > iSerialNumber = 0x0003 <RTUI129S> > bNumConfigurations = 0x0001 > > $ > > does "CT-62B" look reasonable? > Yep, you'll have to add a new entry to usbdevs for the the 0x9e56 device. CT62B seems like a good name (can't put the dash in the name for C syntax reasons). -- Ian > > Regards, > > -Burton > > On Wed, Nov 11, 2015 at 4:38 PM, Ian Lepore <ian@freebsd.org> wrote: > > > 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 digging to try to fix my own error. > > > > > > Here's a diff of the original source and my modified source: > > > > > > [/usr/src/sys/dev/usb/serial]$ /usr/bin/diff ./uftdi.c > > > ./uftdi.c.ORIG > > > 914d913 > > > < UFTDI_DEV(2100, 9e56, 0), > > > [/usr/src/sys/dev/usb/serial]$ > > > > > > Here's the compile splattage: > > > > The VID and PID names are in the file src/sys/dev/usb/usbdevs. > > > > -- Ian > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1447279455.91061.24.camel>