From owner-freebsd-usb@FreeBSD.ORG Sun Jan 30 09:32:20 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C68B106566B for ; Sun, 30 Jan 2011 09:32:20 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id E12AB8FC12 for ; Sun, 30 Jan 2011 09:32:19 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=oR3+9dOmPeF3nZCt5Gxyvf/bIpfj8bfjGZkkfp/xES8= c=1 sm=1 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=TG1YlBi22_1LU6-mEYgA:9 a=s7oGwxzlwlcyA_8p0tIA:7 a=1YihwUX77GH7cMM6VTDV53NacnsA:4 a=PUjeQqilurYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 80960250; Sun, 30 Jan 2011 10:32:18 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 30 Jan 2011 10:32:22 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <20110130003201.GA99514@server.vk2pj.dyndns.org> In-Reply-To: <20110130003201.GA99514@server.vk2pj.dyndns.org> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201101301032.22364.hselasky@c2i.net> Cc: Subject: Re: ACM interface on TI Launchpad X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2011 09:32:20 -0000 On Sunday 30 January 2011 01:32:01 Peter Jeremy wrote: > I recently acquired a TI LaunchPad[1] and want to use FreeBSD as my > development enviroment (for anyone else who is interested in this, at > some stage I intend to post my experiences with the various ports to > -ports or feel free to contact me off-list). It provides a FET430UIF > USB interface to the host computer and some googling shows that this > is a Communication Device Class (CDC), Abstract Control Model (ACM) > sub-class which is supported in Linux via the cdc_acm driver. > > On FreeBSD 8.1, umodem(4) reports: > ugen0.2: at usbus0 > umodem0: on usbus0 > umodem0: data interface 0, has no CM over data, has no break > and creates /dev/ttyU0 (and friends) but mspdebug reports that it > cannot access the UIF (so it is presumably talking to the device > UART, rather than the control interface). > > I have tried adding the device id to usbdevs and > {USB_VPI(USB_VENDOR_TI, USB_PRODUCT_TI_FET430UIF, 1)}, > to sys/dev/usb/serial/umodem.c:umodem_devs[] and this changes the > probe to: > ugen4.2: at usbus4 > umodem0: on usbus4 > umodem0: data interface 0, has no CM over data, has no break > umodem1: on usbus4 > umodem1: Missing descriptor. Assuming data interface is next. > umodem1: data interface 2, has CM over data, has no break > umodem1: no data interface > device_attach: umodem1 attach returned 6 > umodem1: on usbus4 > umodem1: Missing descriptor. Assuming data interface is next. > umodem1: data interface 2, has CM over data, has no break > umodem1: no data interface > device_attach: umodem1 attach returned 6 > but there's no change to the accessibility. Hi, There is a patch pending for allowing a CDC modem interface not having the correct descriptors to work. It is not yet committed. You could try adding the VID+PID to u3g.c. Basically, your modem should have worked, given that the manufacturer had followed the specs. Another alternative is to use LibUSB. Could you remind me about this issue in one week or so? --HPS