Re: How to access a FTDI usb device with a custom vendor and product id's
Thank you for the suggestion ; I already knew about this option, but have intentionally chosen not to use it. Once the VIP/PID is changed, it will no longer work with the Windows app that came with the cable to program the radio (Yaesu FT-897d). When I choose to sell the radio, then I want to be able to sell this cable/software with the radio. I also have a laptop (infected with Windows 7) which I use when I take the radio out for "Field Day" every June. I know I can change the FTDI chip back to it's original configuration, but I am assuming there is a limit to the number of times it can be changed. Regards, -Burton On Thu, Nov 19, 2015 at 7:30 AM, Terje Elde wrote: > > > On 10 Nov 2015, at 17:28, Burton Sampley wrote: > > > > I am having problems getting > > a a FTDI based USB to serial cable to provide CAT control to my Yaesu > > FT-897d amateur radio. The cable is made by RT-Systems with vendor ID > > 0x2100 and a product ID 0x9e56 > > Certainly not suitable to all situations but, if you prefer, it's often > possible to change VID/PID if FTDI-chips. > > Just thought I'd mention as an apropos. > > Terje -- Your mind is like a parachute, it works much better when it is open. ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
> On 10 Nov 2015, at 17:28, Burton Sampley wrote: > > I am having problems getting > a a FTDI based USB to serial cable to provide CAT control to my Yaesu > FT-897d amateur radio. The cable is made by RT-Systems with vendor ID > 0x2100 and a product ID 0x9e56 Certainly not suitable to all situations but, if you prefer, it's often possible to change VID/PID if FTDI-chips. Just thought I'd mention as an apropos. Terje ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
On 11/18/15 20:02, Burton Sampley wrote: To All, A quick update: I really have no update. I have been attempting to get to the point where I can test the newly built module, but I can not get my system to the point where I can try the new module. I was able to compile it, but when I attempted to load the new module, I get the following error: # /usr/bin/grep uftdi /var/log/messages Nov 12 08:14:39 gentoo kernel: KLD uftdi.ko: depends on kernel - not available or version mismatch # I then updated my system and source code, now the kernel will not compile. I searched and found a few posts on one of the FreeBSD forums, which stated the problems might be resolved by "buildworld" first, then "buildkernel", "install kernel", reboot single-user and "installworld". After the latest update and reboot, "buildworld" fails. I don't want to move on to "buildkernel" until I can resolve the "buildworld" failure first. Hi, You only need to build a new kernel. make -m $PWD/share/mk kernel-toolchain -j8 make -m $PWD/share/mk buildkernel -j8 --HPS ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
To All, A quick update: I really have no update. I have been attempting to get to the point where I can test the newly built module, but I can not get my system to the point where I can try the new module. I was able to compile it, but when I attempted to load the new module, I get the following error: # /usr/bin/grep uftdi /var/log/messages Nov 12 08:14:39 gentoo kernel: KLD uftdi.ko: depends on kernel - not available or version mismatch # I then updated my system and source code, now the kernel will not compile. I searched and found a few posts on one of the FreeBSD forums, which stated the problems might be resolved by "buildworld" first, then "buildkernel", "install kernel", reboot single-user and "installworld". After the latest update and reboot, "buildworld" fails. I don't want to move on to "buildkernel" until I can resolve the "buildworld" failure first. # /usr/sbin/freebsd-update fetch Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 10.2-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 10.2-RELEASE-p7. # Made sure my source code is proper and up to date: # /usr/local/bin/svn info Path: . Working Copy Root Path: /usr/src URL: https://svn.freebsd.org/base/stable/10 Relative URL: ^/stable/10 Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 291024 Node Kind: directory Schedule: normal Last Changed Author: gjb Last Changed Rev: 290995 Last Changed Date: 2015-11-17 13:22:56 -0500 (Tue, 17 Nov 2015) # /usr/local/bin/svn update /usr/src Updating '.': At revision 291024. # In between each failed "buildworld" attempt, I have followed the instructions for resetting /usr/obj in the handbook in the "buildworld" ( https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html) section. Here's where "buildworld" fails: --- ===> usr.sbin/pw (all) cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -c /usr/src/usr.sbin/pw/pw.c -o pw.o /usr/src/usr.sbin/pw/pw.c:90:21: error: tentative definition of variable with internal linkage has incomplete non-array type 'struct cargs' [-Werror,-Wtentative-definition-incomplete-type] static struct cargs arglist; ^ --- I assume my issues are outside of the scope of this specific list, but I can not test the simple changes to the uftdi.ko module if I can't get the module to build and load into the running kernel. Here's my current kernel (don't be deceived by the hostname, it's FreeBSD... the hardware used to run Gentoo and I was too lazy to change the hostname/IP on my internal DNS server - which is also running FreeBSD): # /usr/bin/uname -a FreeBSD gentoo.chicken.fish 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 14:19:39 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # What am I missing, or can someone please point me in the right direction of how to successfully "buildworld" so I can then, build a GENERIC kernel and install everything? BTW, I for the kernel build file, I simply made a copy of GENERIC, with a new name and no other modifications. Regards, -Burton On Wed, Nov 11, 2015 at 5:04 PM, Ian Lepore wrote: > 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_VX70x9e52 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: at usbus2, cfg=0 md=HOST > > spd=FULL > > (12Mbps) pwr=ON (90mA) > > > > bLength = 0x0012 > > bDescriptorType = 0x0001 > > bcdUSB = 0x0200 > > bDeviceClass = 0x > > bDeviceSubClass = 0x > > bDeviceProtocol = 0x > > bMaxPacketSize0 = 0x0008
Re: How to access a FTDI usb device with a custom vendor and product id's
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_VX70x9e52 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: at usbus2, cfg=0 md=HOST > spd=FULL > (12Mbps) pwr=ON (90mA) > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x > bDeviceSubClass = 0x > bDeviceProtocol = 0x > bMaxPacketSize0 = 0x0008 > idVendor = 0x2100 > idProduct = 0x9e56 > bcdDevice = 0x0600 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0003 > 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 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 > > > > > ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
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_VX70x9e52 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: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x2100 idProduct = 0x9e56 bcdDevice = 0x0600 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 $ does "CT-62B" look reasonable? Regards, -Burton On Wed, Nov 11, 2015 at 4:38 PM, Ian Lepore 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 > -- Your mind is like a parachute, it works much better when it is open. ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
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 ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
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",
RUN+="/sbin/modprobe -q
ftdi_sio vendor=0x2100 product=0x9e56"
How do I accomplish the same in FreeBSD? When the cable is plugged
in, I
get the following in /var/log/messages:
>>>
>>>
>>> Hi,
>>>
>>> See examples here:
>>>
>>> https://svnweb.freebsd.org/ports/head/multimedia/webcamd/files/webcam
>>> d.conf.in?view=markup
>>>
>>> --HPS
>>
>>
>> But the info in those examples won't cause the uftdi driver to attach
>> to the device (as shown in the linux-based example), that can only
>> happen if the vid/pid are added to the table in the driver itself,
>> right? I don't remember any mechanism in our usb world for forcing a
>> driver to attach to a device that isn't compiled into the driver's
>> usb_device_id array.
>>
>> On the other hand, if the device is going to be accessed via libusb
>> and/or libftdi, I'm not sure the tty driver needs to attach to it at
>> all; don't those libraries work purely through the ugen device?
>>
>
> Right. This might be a feature for:
>
> https://reviews.freebsd.org/D3458
No. That's different. I need to integrate the code from my talk a few years
ago
that did the right mappings so the device driver knew what to do with the
device.
Warner
> --HPS
>
>
> ___
> freebsd-usb@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-usb
> To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
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:
===> usb/uftdi (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -gdwarf-2
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
-Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs
-fdiagnostics-show-option -Wno-error-tautological-compare
-Wno-error-empty-body -Wno-error-parentheses-equality
-Wno-error-unused-function -c
/usr/src/sys/modules/usb/uftdi/../../../dev/usb/serial/uftdi.c -o uftdi.o
/usr/src/sys/modules/usb/uftdi/../../../dev/usb/serial/uftdi.c:914:2:
error: use of undeclared identifier 'USB_VENDOR_2100'
UFTDI_DEV(2100, 9e56, 0),
^
/usr/src/sys/modules/usb/uftdi/../../../dev/usb/serial/uftdi.c:275:13:
note: expanded from macro 'UFTDI_DEV'
{ USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, i) }
^
:167:1: note: expanded from here
USB_VENDOR_2100
^
@/dev/usb/usbdi.h:332:14: note: expanded from macro 'USB_VPI'
USB_VENDOR(vend), USB_PRODUCT(prod), USB_DRIVER_INFO(info)
^
@/dev/usb/usbdi.h:323:40: note: expanded from macro 'USB_VENDOR'
.match_flag_vendor = 1, .idVendor = (vend)
^
/usr/src/sys/modules/usb/uftdi/../../../dev/usb/serial/uftdi.c:914:2:
error: use of undeclared identifier 'USB_PRODUCT_2100_9e56'
/usr/src/sys/modules/usb/uftdi/../../../dev/usb/serial/uftdi.c:275:29:
note: expanded from macro 'UFTDI_DEV'
{ USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, i) }
^
:170:1: note: expanded from here
USB_PRODUCT_2100_9e56
^
@/dev/usb/usbdi.h:332:33: note: expanded from macro 'USB_VPI'
USB_VENDOR(vend), USB_PRODUCT(prod), USB_DRIVER_INFO(info)
^
@/dev/usb/usbdi.h:326:42: note: expanded from macro 'USB_PRODUCT'
.match_flag_product = 1, .idProduct = (prod)
^
/usr/src/sys/modules/usb/uftdi/../../../dev/usb/serial/uftdi.c:1067:48:
error: invalid application of 'sizeof' to an incomplete type 'const struct
usb_device_id []'
id = usbd_lookup_id_by_info(uftdi_devs, sizeof(uftdi_devs),
^~~~
3 errors generated.
*** Error code 1
Stop.
make[5]: stopped in /usr/src/sys/modules/usb/uftdi
*** Error code 1
Stop.
make[4]: stopped in /usr/src/sys/modules/usb
*** Error code 1
Stop.
make[3]: stopped in /usr/src/sys/modules
*** Error code 1
Stop.
make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
*** Error code 1
Stop.
make[1]: stopped in /usr/src
*** Error code 1
Stop.
make: stopped in /usr/src
[/usr/src]$
On Tue, Nov 10, 2015 at 12:20 PM, Hans Petter Selasky
wrote:
> On 11/10/15 18:14, Burton Sampley wrote:
>
>> Thank you. I do not have the kernel source on this system, so I will need
>> to setup the kernel source, then modify the table in uftdi.c with the
>> custom entries, then recompile the module and reload it. It may take some
>> time for me to complete these actions. Should I report back to this email
>> list if this solution resolves my problem?
>>
>
> Hi,
>
> Please keep us updated. Nice to hear some success stories too ;-)
>
> And also there is #bsdusb on EF-net.
>
> --HPS
>
--
Your mind is like a parachute, it works much better when it is open.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
On 11/10/15 18:14, Burton Sampley wrote: Thank you. I do not have the kernel source on this system, so I will need to setup the kernel source, then modify the table in uftdi.c with the custom entries, then recompile the module and reload it. It may take some time for me to complete these actions. Should I report back to this email list if this solution resolves my problem? Hi, Please keep us updated. Nice to hear some success stories too ;-) And also there is #bsdusb on EF-net. --HPS ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
Thank you. I do not have the kernel source on this system, so I will need to setup the kernel source, then modify the table in uftdi.c with the custom entries, then recompile the module and reload it. It may take some time for me to complete these actions. Should I report back to this email list if this solution resolves my problem? Regards, -Burton On Tue, Nov 10, 2015 at 12:01 PM, Hans Petter Selasky wrote: > On 11/10/15 17:55, Burton Sampley wrote: > >> HPS, >> >> Thank you for your prompt response. I reviewed the webpage link you have >> provided. I assume that would be a template for an entry in >> /etc/devd.conf, however what I do not understand is what is the FreeBSD >> equivalent of "FTDI_SIO" that can be called in the "action" line? >> > > Hi, > > FreeBSD doesn't support that you add a VID and PID to a driver runtime. > > >> The first step I would like to accomplish is to simple make the device >> work >> at the command line, then I can automate the steps within /etc/devd.conf. >> Right now, I am struggling to find documentation that is fit-for-purpose >> for USB. I would like to figure out if libftdi is the proper solution or >> if I must use uftdi. If I need to use uftdi, then specifically how do I >> force uftdi to attach to a custom vid/pid? >> > > You will need to add a vendor/product entry in this table: > > > https://svnweb.freebsd.org/base/head/sys/dev/usb/serial/uftdi.c?revision=286385&view=markup#l273 > > --HPS > -- Your mind is like a parachute, it works much better when it is open. ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
On 11/10/15 17:55, Burton Sampley wrote: HPS, Thank you for your prompt response. I reviewed the webpage link you have provided. I assume that would be a template for an entry in /etc/devd.conf, however what I do not understand is what is the FreeBSD equivalent of "FTDI_SIO" that can be called in the "action" line? Hi, FreeBSD doesn't support that you add a VID and PID to a driver runtime. The first step I would like to accomplish is to simple make the device work at the command line, then I can automate the steps within /etc/devd.conf. Right now, I am struggling to find documentation that is fit-for-purpose for USB. I would like to figure out if libftdi is the proper solution or if I must use uftdi. If I need to use uftdi, then specifically how do I force uftdi to attach to a custom vid/pid? You will need to add a vendor/product entry in this table: https://svnweb.freebsd.org/base/head/sys/dev/usb/serial/uftdi.c?revision=286385&view=markup#l273 --HPS ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
HPS,
Thank you for your prompt response. I reviewed the webpage link you have
provided. I assume that would be a template for an entry in
/etc/devd.conf, however what I do not understand is what is the FreeBSD
equivalent of "FTDI_SIO" that can be called in the "action" line?
The first step I would like to accomplish is to simple make the device work
at the command line, then I can automate the steps within /etc/devd.conf.
Right now, I am struggling to find documentation that is fit-for-purpose
for USB. I would like to figure out if libftdi is the proper solution or
if I must use uftdi. If I need to use uftdi, then specifically how do I
force uftdi to attach to a custom vid/pid?
Regards,
-Burton
On Tue, Nov 10, 2015 at 11:40 AM, Hans Petter Selasky
wrote:
> On 11/10/15 17:28, Burton Sampley wrote:
>
>> SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56", RUN+="/sbin/modprobe -q
>> ftdi_sio vendor=0x2100 product=0x9e56"
>>
>> How do I accomplish the same in FreeBSD? When the cable is plugged in, I
>> get the following in /var/log/messages:
>>
>
> Hi,
>
> See examples here:
>
>
> https://svnweb.freebsd.org/ports/head/multimedia/webcamd/files/webcamd.conf.in?view=markup
>
> --HPS
>
--
Your mind is like a parachute, it works much better when it is open.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
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",
RUN+="/sbin/modprobe -q
ftdi_sio vendor=0x2100 product=0x9e56"
How do I accomplish the same in FreeBSD? When the cable is plugged
in, I
get the following in /var/log/messages:
Hi,
See examples here:
https://svnweb.freebsd.org/ports/head/multimedia/webcamd/files/webcam
d.conf.in?view=markup
--HPS
But the info in those examples won't cause the uftdi driver to attach
to the device (as shown in the linux-based example), that can only
happen if the vid/pid are added to the table in the driver itself,
right? I don't remember any mechanism in our usb world for forcing a
driver to attach to a device that isn't compiled into the driver's
usb_device_id array.
On the other hand, if the device is going to be accessed via libusb
and/or libftdi, I'm not sure the tty driver needs to attach to it at
all; don't those libraries work purely through the ugen device?
Right. This might be a feature for:
https://reviews.freebsd.org/D3458
--HPS
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
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",
> > RUN+="/sbin/modprobe -q
> > ftdi_sio vendor=0x2100 product=0x9e56"
> >
> > How do I accomplish the same in FreeBSD? When the cable is plugged
> > in, I
> > get the following in /var/log/messages:
>
> Hi,
>
> See examples here:
>
> https://svnweb.freebsd.org/ports/head/multimedia/webcamd/files/webcam
> d.conf.in?view=markup
>
> --HPS
But the info in those examples won't cause the uftdi driver to attach
to the device (as shown in the linux-based example), that can only
happen if the vid/pid are added to the table in the driver itself,
right? I don't remember any mechanism in our usb world for forcing a
driver to attach to a device that isn't compiled into the driver's
usb_device_id array.
On the other hand, if the device is going to be accessed via libusb
and/or libftdi, I'm not sure the tty driver needs to attach to it at
all; don't those libraries work purely through the ugen device?
-- Ian
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: How to access a FTDI usb device with a custom vendor and product id's
On 11/10/15 17:28, Burton Sampley wrote:
SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56", RUN+="/sbin/modprobe -q
ftdi_sio vendor=0x2100 product=0x9e56"
How do I accomplish the same in FreeBSD? When the cable is plugged in, I
get the following in /var/log/messages:
Hi,
See examples here:
https://svnweb.freebsd.org/ports/head/multimedia/webcamd/files/webcamd.conf.in?view=markup
--HPS
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
How to access a FTDI usb device with a custom vendor and product id's
Greetings,
I am a long time FreeBSD user (started with FreeBSD 2.1.5R). I took a
break with FreeBSD for a while with a Linux desktop, but have recently
returned. I am now running a 10.2R desktop. I am having problems getting
a a FTDI based USB to serial cable to provide CAT control to my Yaesu
FT-897d amateur radio. The cable is made by RT-Systems with vendor ID
0x2100 and a product ID 0x9e56. In Linux, using a udev rule, the cable
works correctly with a command like the following:
modprobe ftdi_sio vendor=0x2100 product=0x9e56
or a udev rule similar to the following:
SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56", RUN+="/sbin/modprobe -q
ftdi_sio vendor=0x2100 product=0x9e56"
How do I accomplish the same in FreeBSD? When the cable is plugged in, I
get the following in /var/log/messages:
Nov 10 08:17:58 kernel: ugen2.3: at usbus2 (disconnected)
Nov 10 08:18:06 kernel: ugen2.3: at usbus2
Nov 10 08:18:06 devd: Executing 'logger Unknown USB device: vendor 0x2100
product 0x9e56 bus uhub4'
Nov 10 08:18:06 root: Unknown USB device: vendor 0x2100 product 0x9e56 bus
uhub4
Nov 10 08:47:31 devd: Executing 'logger Unknown USB device: vendor 0x2100
product 0x9e56 bus uhub4'
Nov 10 08:47:31 root: Unknown USB device: vendor 0x2100 product 0x9e56 bus
uhub4
and usbconfig shows the following:
$ /usr/local/bin/sudo /usr/sbin/usbconfig -d ugen2.3 dump_device_desc
ugen2.3: at usbus2, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (90mA)
bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x
bDeviceSubClass = 0x
bDeviceProtocol = 0x
bMaxPacketSize0 = 0x0008
idVendor = 0x2100
idProduct = 0x9e56
bcdDevice = 0x0600
iManufacturer = 0x0001
iProduct = 0x0002
iSerialNumber = 0x0003
bNumConfigurations = 0x0001
$
I have installed devel/libftdi from the ports collection, but I have not
found documentation on how to configure my system to be able to use this
device.
Once this issue is resolved, I want to use hamlib or FLRIG and FLDIGI for
amateur radio digital communications.
I have been searching for days to find documentation on what I need to do
to make this work and have struck out.
Regards,
-Burton
--
Your mind is like a parachute, it works much better when it is open.
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
