From owner-freebsd-usb@freebsd.org  Tue Nov 10 16:50:14 2015
Return-Path: <owner-freebsd-usb@freebsd.org>
Delivered-To: freebsd-usb@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71EB1A2B8FD
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Tue, 10 Nov 2015 16:50:14 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org
 [54.200.247.200])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5315F1F0B
 for <freebsd-usb@freebsd.org>; Tue, 10 Nov 2015 16:50:14 +0000 (UTC)
 (envelope-from ian@freebsd.org)
Received: from ilsoft.org (unknown [73.34.117.227])
 by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA;
 Tue, 10 Nov 2015 16:50:20 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.14.9/8.14.9) with ESMTP id tAAGoBK6003727;
 Tue, 10 Nov 2015 09:50:11 -0700 (MST) (envelope-from ian@freebsd.org)
Message-ID: <1447174212.91061.9.camel@freebsd.org>
Subject: Re: How to access a FTDI usb device with a custom vendor and
 product id's
From: Ian Lepore <ian@freebsd.org>
To: Hans Petter Selasky <hps@selasky.org>, Burton Sampley <bsmply@gmail.com>,
 freebsd-usb@freebsd.org
Date: Tue, 10 Nov 2015 09:50:12 -0700
In-Reply-To: <56421DFD.6070503@selasky.org>
References: <CANV5k3rW62rGoXKD4m5meegEJ04T4b_v=QGCqBV5wuGxZjzCbg@mail.gmail.com>
 <56421DFD.6070503@selasky.org>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Nov 2015 16:50:14 -0000

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