From owner-freebsd-usb@FreeBSD.ORG Fri Nov 12 14:24:12 2010 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 5C7E51065670 for ; Fri, 12 Nov 2010 14:24:12 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id DD0DD8FC08 for ; Fri, 12 Nov 2010 14:24:11 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yevn+QCjI6xy199BDvBOOiO14qYvyLq62he9tTtU3M8= c=1 sm=1 a=eA1fqfAm1u4A:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=hzqryNHT1mifrWZN93UA:9 a=izL0aM0AdDz_Itp6rtFE6v0D1z4A:4 a=wPNLvfGTeEIA: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 48343578; Fri, 12 Nov 2010 15:24:10 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 12 Nov 2010 15:25:13 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.4.5; amd64; ; ) References: <20101112145849.161e39a8@davenulle.org> In-Reply-To: <20101112145849.161e39a8@davenulle.org> X-Face: +~\`s("[*|O,="7?X@L.elg*F"OA\I/3%^p8g?ab%RN'(; _IjlA: hGE..Ew, XAQ*o#\/M~SC=S1-f9{EzRfT'|Hhll5Q]ha5Bt-s|oTlKMusi:1e[wJl}kd}GR Z0adGx-x_0zGbZj'e(Y[(UNle~)8CQWXW@:DX+9)_YlB[tIccCPN$7/L' MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011121525.13324.hselasky@c2i.net> Cc: Subject: Re: uplcom(4) does not work on cuaU0 ? 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: Fri, 12 Nov 2010 14:24:12 -0000 On Friday 12 November 2010 14:58:49 Patrick Lamaiziere wrote: > (8.1-STABLE/i386) > > Hello, > > Here, if uplcom is attached to cuaU0, the serial connection does not > work, as far i can see it does not send anything : > > kernel: uplcom_pre_param: > kernel: uplcom_cfg_param: sc = 0xc7416200 > kernel: uplcom_cfg_param: rate=9600 fmt=0 parity=0 bits=8 > kernel: uplcom_pre_param: > kernel: uplcom_cfg_set_dtr: onoff = 1 > kernel: uplcom_cfg_set_rts: onoff = 1 > kernel: uplcom_cfg_param: sc = 0xc7416200 > kernel: uplcom_cfg_param: rate=57600 fmt=0 parity=0 bits=8 > > that's all > > But if attached to cuaU3, it works fine. The difference is the use > of an u3g key using cuaU0. > > kernel: ugen0.3: at usbus0 > kernel: uplcom0: class 0/0, rev 1.10/3.00, addr 3> on usbus0 > kernel: uplcom_attach: sc = 0xc7417c00 > kernel: uplcom_attach: chiptype: 2303X > kernel: uplcom_pre_param: > kernel: uplcom_cfg_set_dtr: onoff = 1 > kernel: uplcom_pre_param: > kernel: uplcom_intr_callback: actlen = 10 > kernel: uplcom_intr_callback: status = 0x82 > kernel: uplcom_cfg_set_rts: onoff = 1 > kernel: uplcom_cfg_set_break: onoff = 0 > kernel: uplcom_cfg_get_status: > kernel: uplcom_cfg_param: sc = 0xc7417c00 > kernel: uplcom_cfg_param: rate=9600 fmt=0 parity=0 bits=8 > kernel: uplcom_cfg_param: sc = 0xc7417c00 > kernel: uplcom_cfg_param: rate=57600 fmt=0 parity=0 bits=8 > kernel: uplcom_cfg_get_status: > kernel: uplcom_cfg_set_dtr: onoff = 1 > kernel: uplcom_cfg_set_dtr: onoff = 0 > kernel: uplcom_cfg_set_rts: onoff = 1 > kernel: uplcom_cfg_set_dtr: onoff = 1 > kernel: uplcom_cfg_set_rts: onoff = 1 > kernel: uplcom_write_callback: actlen = 1 > kernel: uplcom_write_callback: actlen = 1 > kernel: uplcom_write_callback: actlen = 32 Hi, Maybe the device detection logic in sys/dev/usb/serial/uplcom.c is not correct. Could you dump usbconfig output from your device? usbconfig -d X.Y dump_device_desc --HPS