From owner-freebsd-usb@freebsd.org Wed Nov 11 21:32:16 2015 Return-Path: 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 4E3DEA2C176 for ; Wed, 11 Nov 2015 21:32:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F14351564 for ; Wed, 11 Nov 2015 21:32:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by qgad10 with SMTP id d10so33988929qga.3 for ; Wed, 11 Nov 2015 13:32:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp_com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=KG9rmsMD+e/vE/hqoTyv8ff4O43IwNea9In3/Sc1QfQ=; b=OXxyYQxa6Gz6Yh3f1+6N0HlF/AhOnIpjeA2UZa5AyKerxIOkWLxGNLpvg8HGXGsw0O dHIw0/NrrdBFwCzRc/gLx15PWwsR4RtaDNs30qOHmCqkwb8UYm5vPpDdpj6noB8d0hRW VeHQbrY+ZwpDivoS3wCi+DK9KcjyNw5uvAxDSiXIb3krDDJ3OitEG9V/gTeuns4mg0ju zefmsm59yYeNwO2FMlT9vb1kIjMcVMLdh/aiu9q1YtLlPxDGOMdJliUc5L0ozkP/t5V8 vAGdyjzB+cvLnbDoHLi476n/J5CxtGCXZhFNyi8UXloG6tctXfUaN5WpZUc3HFQmBSCb XSSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=KG9rmsMD+e/vE/hqoTyv8ff4O43IwNea9In3/Sc1QfQ=; b=bsyARP0HXeTfmyggfiR1Ntzslvxroblavu0dUovykFLXaMYE4ReLo4HrNfqWWsizrp i4M2XRD569pgL8UYrsM/OKbwd2QrtAE77O/MEHs5/6pn/sc4AUHJRy/RD2hF618FUMNU XzhYFAyKJ7v9pJu34MC5vK0a7YMmZzQubq7cfy43Jto5CrSdBECY1+hBSH6OENp8uZf5 zee/26qgHeMxH11MsOe5Iz/IlNm6nZ3mEx0tFDZubkLCIq3ZWQHDOvBEKKNGsU0sYjt0 VaWZq7QZLFjIOxtbbwL9B8gtrJeH1APEF0vzdvRIJsMDQZ0AD+3DfC82fdBfwpbzIoQ3 OAGw== X-Gm-Message-State: ALoCoQlhS05yz0YhsP78SexM+vtpb6letDGMOonZU31ncfKdr3kmclIvISolD7NqFGf5GC09KSbl MIME-Version: 1.0 X-Received: by 10.140.234.134 with SMTP id f128mr13926472qhc.43.1447277534721; Wed, 11 Nov 2015 13:32:14 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.140.27.181 with HTTP; Wed, 11 Nov 2015 13:32:14 -0800 (PST) X-Originating-IP: [2607:fb90:181:948c:0:8:a70c:3501] Received: by 10.140.27.181 with HTTP; Wed, 11 Nov 2015 13:32:14 -0800 (PST) In-Reply-To: <56422167.6050803@selasky.org> References: <56421DFD.6070503@selasky.org> <1447174212.91061.9.camel@freebsd.org> <56422167.6050803@selasky.org> Date: Wed, 11 Nov 2015 14:32:14 -0700 X-Google-Sender-Auth: ztaB6l5-6VYawzhPF04Ouo4ZHzs Message-ID: Subject: Re: How to access a FTDI usb device with a custom vendor and product id's From: Warner Losh To: Hans Petter Selasky Cc: Burton Sampley , Ian Lepore , freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 21:32:16 -0000 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-unsubscribe@freebsd.org"