From owner-freebsd-current@FreeBSD.ORG Wed Jun 2 00:41:34 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 511F1106567B for ; Wed, 2 Jun 2010 00:41:34 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0884A8FC13 for ; Wed, 2 Jun 2010 00:41:33 +0000 (UTC) Received: by gwj23 with SMTP id 23so4748106gwj.13 for ; Tue, 01 Jun 2010 17:41:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=eFwEpXWMgpHZ+i/VFsl7sa2pppNV4jla0Rgt8N+gVpc=; b=kT4NTL0M1/Jo84mnmxTPI8ttLOd6C10PqzHptuSWbQ+4nQF84haIcU8vooIgbcTlkF H+007VvxqM5k5Imgr576WfhDoydpfK7Cjd0URrWhb0YS0eeVrT82hLV/oGaEt0Db9ueL qdQSWjxJtUC84WgptSJWe7EqbrPXqs7qc34vs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=P0gn7kiPBfa7LRA6Jmt4MzhdJLSVLqcUZYO1XRPkbnh+UzrZM/Lx54EQE9OqKzX6uX diXol+vU8FO6nLQ1Hy5f9Tj3kTP/PGzqAbexHVpBVQpP5csLLJdKyH5W8EjGF4seSsCB tIAJ2F8ytzgykvVeAQMAWt0nfOtKlkJLs8jaw= MIME-Version: 1.0 Received: by 10.224.58.152 with SMTP id g24mr2961389qah.382.1275439292591; Tue, 01 Jun 2010 17:41:32 -0700 (PDT) Received: by 10.229.89.148 with HTTP; Tue, 1 Jun 2010 17:41:32 -0700 (PDT) Date: Tue, 1 Jun 2010 21:41:32 -0300 Message-ID: From: "Marcelo/Porks" To: current Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: umodem (4) recognize a CDC-ACM device X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2010 00:41:34 -0000 Hi guys. I have a device[1] that is recognized on Linux by the generic CDC-ACM driver and I'm trying to do the same on FreeBSD current with umodem (4). But, as you can see, I had no success: Jun 1 20:00:54 BARAD-DUR kernel: uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT Jun 1 20:00:54 BARAD-DUR kernel: uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 Jun 1 20:00:55 BARAD-DUR kernel: ugen0.3: at usbus0 Jun 1 20:00:55 BARAD-DUR kernel: umodem0: on usbus0 Jun 1 20:00:55 BARAD-DUR kernel: umodem0: data interface 1, has CM over data, has no break Jun 1 20:00:55 BARAD-DUR kernel: device_attach: umodem0 attach returned 6 Jun 1 20:00:55 BARAD-DUR kernel: umodem0: on usbus0 Jun 1 20:00:55 BARAD-DUR kernel: umodem0: data interface 1, has CM over data, has no break Jun 1 20:00:55 BARAD-DUR kernel: device_attach: umodem0 attach returned 6 Have you some tip for me to make this work on FreeBSD? I had put some 'printf' at the source code and noticed that umodem_attach() failed at line 378 [2]. The main reason is basically that the usbd_transfer_setup() got an endpoint [3] with 'ep->methods == NULL' [4] and this leads to "USB_ERR_NO_PIPE" on [5]. Thanks. [1] http://www.recursion.jp/avrcdc/driver.html#linux [2] http://fxr.watson.org/fxr/source/dev/usb/serial/umodem.c#L378 [3] http://fxr.watson.org/fxr/source/dev/usb/usb_transfer.c#L877 [4] http://fxr.watson.org/fxr/source/dev/usb/usb_transfer.c#L880 [5] http://fxr.watson.org/fxr/source/dev/usb/usb_transfer.c#L886 -- Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights."