From owner-freebsd-usb@freebsd.org  Tue Nov 10 16:59:31 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 C51DCA2BBE8
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Tue, 10 Nov 2015 16:59:31 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214])
 (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 86E2512F5
 for <freebsd-usb@freebsd.org>; Tue, 10 Nov 2015 16:59:31 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from laptop015.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 800391FE022;
 Tue, 10 Nov 2015 17:59:29 +0100 (CET)
Subject: Re: How to access a FTDI usb device with a custom vendor and product
 id's
To: Burton Sampley <bsmply@gmail.com>
References: <CANV5k3rW62rGoXKD4m5meegEJ04T4b_v=QGCqBV5wuGxZjzCbg@mail.gmail.com>
 <56421DFD.6070503@selasky.org>
 <CANV5k3oRPP_-_SBz2fih0tA12BzoO9Ua+AfJGaE_CCNE3JzpHQ@mail.gmail.com>
Cc: freebsd-usb@freebsd.org
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <564222D8.6020900@selasky.org>
Date: Tue, 10 Nov 2015 18:01:12 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CANV5k3oRPP_-_SBz2fih0tA12BzoO9Ua+AfJGaE_CCNE3JzpHQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
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:59:31 -0000

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