From owner-freebsd-stable@FreeBSD.ORG Mon Feb 4 21:15:09 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5A31BA90 for ; Mon, 4 Feb 2013 21:15:09 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 2BFD3FB4 for ; Mon, 4 Feb 2013 21:15:05 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r14LF4mx089972 for ; Mon, 4 Feb 2013 14:15:04 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r14LF2kh029826; Mon, 4 Feb 2013 14:15:02 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: So I whip out a FTDI-based multiport Serial USB Adapter.... From: Ian Lepore To: CeDeROM In-Reply-To: References: <511004AA.3060201@denninger.net> <1360008362.93359.485.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Feb 2013 14:15:02 -0700 Message-ID: <1360012502.93359.491.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Feb 2013 21:15:09 -0000 On Mon, 2013-02-04 at 22:05 +0100, CeDeROM wrote: > On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore wrote: > > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > > parts program different vendor/product info and IDs have to be added to > > code to recognize them, that's the only trouble one usually encounters. > > I also want to use my KT-LINK multipurpose low-level embedded access > multitool based on FT2232H with RS232 port and I was worried there is > no driver - right now I will add the PID and recompile sources to see > if it works - happy to catch this thread :-) > > Some questions as you Ian seem to already have experience with this devices: > 1. Is it possible to compile only uftdi driver and load it into > existing kernel that have this driver compiled-in so I don't have to > recompile whole kernel and all of the modules? > 2. Is it possible to pass VID/PID and/or RS232 channel as kernel > loadable option? This would again spare some build/runtime time for me > :-) > 3. Do you know a good method on kernel module testing other than > rebuilding/rebooting all the time? VirtualBox + USB Attach? > > Any hints appreciated! :-) > Tomek > If you don't already have the right devices compiled in, just build the usb/ucom and usb/uftdi modules and kldload uftdi and you should be good to go. -- Ian