From owner-freebsd-usb@FreeBSD.ORG Sun May 27 15:40:05 2007 Return-Path: X-Original-To: freebsd-usb@hub.freebsd.org Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0416416A477 for ; Sun, 27 May 2007 15:40:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D106513C46E for ; Sun, 27 May 2007 15:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4RFe4oO022973 for ; Sun, 27 May 2007 15:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4RFe410022972; Sun, 27 May 2007 15:40:04 GMT (envelope-from gnats) Resent-Date: Sun, 27 May 2007 15:40:04 GMT Resent-Message-Id: <200705271540.l4RFe410022972@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-usb@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ulrich Spoerlein Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A724416A47F for ; Sun, 27 May 2007 15:33:20 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 1985113C465 for ; Sun, 27 May 2007 15:33:19 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so691864uge for ; Sun, 27 May 2007 08:33:19 -0700 (PDT) Received: by 10.67.115.7 with SMTP id s7mr4563609ugm.1180279999159; Sun, 27 May 2007 08:33:19 -0700 (PDT) Received: from coyote.q.local ( [85.180.181.200]) by mx.google.com with ESMTP id a1sm4081087ugf.2007.05.27.08.33.17; Sun, 27 May 2007 08:33:18 -0700 (PDT) Received: from coyote.q.local (localhost [127.0.0.1]) by coyote.q.local (8.14.1/8.13.8) with ESMTP id l4RFXF2L002562; Sun, 27 May 2007 17:33:15 +0200 (CEST) (envelope-from q@coyote.q.local) Received: (from q@localhost) by coyote.q.local (8.14.1/8.13.8/Submit) id l4RFXF4e002561; Sun, 27 May 2007 17:33:15 +0200 (CEST) (envelope-from q) Message-Id: <200705271533.l4RFXF4e002561@coyote.q.local> Date: Sun, 27 May 2007 17:33:15 +0200 (CEST) From: Ulrich Spoerlein To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Hans Petter Selasky Subject: usb/113060: Samsung printer not working in bidirectional mode 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, 27 May 2007 15:40:05 -0000 >Number: 113060 >Category: usb >Synopsis: Samsung printer not working in bidirectional mode >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun May 27 15:40:04 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Ulrich Spörlein >Release: FreeBSD 6.2-STABLE i386 >Organization: >Environment: >Description: The following printer, when attached via USB fails to work port 2 addr 2: full speed, self powered, config 1, SAMSUNG Laser Printer ML-4600(0x3004), SAMSUNG ELECTRONICS CO., LT(0x04e8), rev 1.00 Peter van Heusden identified the problem to be the bi-directional mode. When adding the quirks as given below *OR* chmod a-w /dev/ulpt0 CUPS will print just fine. Please note that under the new USB stack developed by Hans Petter Selasky the printer works out of the box. This, and usb/112944 leave me to believe it is a more general problem with bidirectional support under ulpt(4). Perhaps HPS can comment on the architectural differences between the old and his new ulpt(4)? PS: Whitespace and sorting in usb_quirks.c are, well, interessting. >How-To-Repeat: >Fix: --- ml4600.diff begins here --- Index: usb_quirks.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/usb_quirks.c,v retrieving revision 1.41.2.8 diff -u -p -r1.41.2.8 usb_quirks.c --- usb_quirks.c 28 Apr 2007 20:31:30 -0000 1.41.2.8 +++ usb_quirks.c 27 May 2007 15:31:37 -0000 @@ -99,6 +99,7 @@ Static const struct usbd_quirk_entry { { USB_VENDOR_HP, USB_PRODUCT_HP_810C, ANY, { UQ_BROKEN_BIDIR }}, { USB_VENDOR_HP, USB_PRODUCT_HP_830C, ANY, { UQ_BROKEN_BIDIR }}, { USB_VENDOR_HP, USB_PRODUCT_HP_1220C, ANY, { UQ_BROKEN_BIDIR }}, + { USB_VENDOR_SAMSUNG, USB_PRODUCT_SAMSUNG_ML4600, ANY, { UQ_BROKEN_BIDIR }}, { USB_VENDOR_XEROX, USB_PRODUCT_XEROX_WCM15, ANY, { UQ_BROKEN_BIDIR }}, /* YAMAHA router's ucdDevice is the version of farmware and often changes. */ { USB_VENDOR_YAMAHA, USB_PRODUCT_YAMAHA_RTA54I, Index: usbdevs =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/usbdevs,v retrieving revision 1.232.2.24 diff -u -p -r1.232.2.24 usbdevs --- usbdevs 20 May 2007 12:34:39 -0000 1.232.2.24 +++ usbdevs 27 May 2007 09:30:30 -0000 @@ -1491,6 +1491,7 @@ product RATOC REXUSB60 0xb000 REX-USB60 product SAGEM USBSERIAL 0x0027 USB-Serial Controller /* Samsung products */ +product SAMSUNG ML4600 0x3004 ML-4600 laser printer product SAMSUNG ML6060 0x3008 ML-6060 laser printer /* SanDisk products */ --- ml4600.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-usb@FreeBSD.ORG Sun May 27 20:32:51 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F99616A494 for ; Sun, 27 May 2007 20:32:51 +0000 (UTC) (envelope-from hselasky@freebsd.org) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id D52BA13C46C for ; Sun, 27 May 2007 20:32:50 +0000 (UTC) (envelope-from hselasky@freebsd.org) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe08.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 501320151; Sun, 27 May 2007 22:32:47 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 27 May 2007 22:32:32 +0200 User-Agent: KMail/1.9.5 References: <200705271533.l4RFXF4e002561@coyote.q.local> In-Reply-To: <200705271533.l4RFXF4e002561@coyote.q.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200705272232.32410.hselasky@freebsd.org> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: usb/113060: Samsung printer not working in bidirectional mode 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, 27 May 2007 20:32:51 -0000 On Sunday 27 May 2007 17:33, Ulrich Spoerlein wrote: > >Number: 113060 > >Category: usb > >Synopsis: Samsung printer not working in bidirectional mode > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sun May 27 15:40:04 GMT 2007 > >Closed-Date: > >Last-Modified: > >Originator: Ulrich Sp=F6rlein > >Release: FreeBSD 6.2-STABLE i386 > >Organization: > >Environment: > >Description: > > The following printer, when attached via USB fails to work > > port 2 addr 2: full speed, self powered, config 1, SAMSUNG Laser Printer > ML-4600(0x3004), SAMSUNG ELECTRONICS CO., LT(0x04e8), rev 1.00 > > Peter van Heusden identified the problem to be the bi-directional mode. > When adding the quirks as given below *OR* chmod a-w /dev/ulpt0 CUPS will > print just fine. > > Please note that under the new USB stack developed by Hans Petter Selasky > the printer works out of the box. This, and usb/112944 leave me to believe > it is a more general problem with bidirectional support under ulpt(4). > > Perhaps HPS can comment on the architectural differences between the old > and his new ulpt(4)? > > PS: Whitespace and sorting in usb_quirks.c are, well, interessting. > > >How-To-Repeat: > >Fix: > > --- ml4600.diff begins here --- > Index: usb_quirks.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/dev/usb/usb_quirks.c,v > retrieving revision 1.41.2.8 > diff -u -p -r1.41.2.8 usb_quirks.c > --- usb_quirks.c 28 Apr 2007 20:31:30 -0000 1.41.2.8 > +++ usb_quirks.c 27 May 2007 15:31:37 -0000 > @@ -99,6 +99,7 @@ Static const struct usbd_quirk_entry { > { USB_VENDOR_HP, USB_PRODUCT_HP_810C, ANY, { UQ_BROKEN_BIDIR }}, > { USB_VENDOR_HP, USB_PRODUCT_HP_830C, ANY, { UQ_BROKEN_BIDIR }}, > { USB_VENDOR_HP, USB_PRODUCT_HP_1220C, ANY, { UQ_BROKEN_BIDIR }}, > + { USB_VENDOR_SAMSUNG, USB_PRODUCT_SAMSUNG_ML4600, ANY, { > UQ_BROKEN_BIDIR }}, { USB_VENDOR_XEROX, USB_PRODUCT_XEROX_WCM15, ANY,= =20 > { UQ_BROKEN_BIDIR }}, /* YAMAHA router's ucdDevice is the version of > farmware and often changes. */ { USB_VENDOR_YAMAHA, > USB_PRODUCT_YAMAHA_RTA54I, > Index: usbdevs > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/dev/usb/usbdevs,v > retrieving revision 1.232.2.24 > diff -u -p -r1.232.2.24 usbdevs > --- usbdevs 20 May 2007 12:34:39 -0000 1.232.2.24 > +++ usbdevs 27 May 2007 09:30:30 -0000 > @@ -1491,6 +1491,7 @@ product RATOC REXUSB60 0xb000 REX-USB60 > product SAGEM USBSERIAL 0x0027 USB-Serial Controller > > /* Samsung products */ > +product SAMSUNG ML4600 0x3004 ML-4600 laser printer > product SAMSUNG ML6060 0x3008 ML-6060 laser printer > > /* SanDisk products */ > --- ml4600.diff ends here --- > > >Release-Note: > >Audit-Trail: > >Unformatted: > Hi, The main difference between the old "ulpt" and the new "ulpt" is that the n= ew=20 use asynchronous reading of data, while the old "ulpt" uses synchronous=20 reading. That means that the new "ulpt" transfers data to/from all endpoint= s=20 in the background. Maybe that has something to do with the problem, that the IN enpoint is not= =20 polled. =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Sun May 27 20:35:59 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0523216A468 for ; Sun, 27 May 2007 20:35:59 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 9B69E13C44C for ; Sun, 27 May 2007 20:35:58 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe04.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 502139678 for freebsd-usb@freebsd.org; Sun, 27 May 2007 22:35:55 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 27 May 2007 22:35:46 +0200 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705272235.46048.hselasky@c2i.net> Subject: 31st address line sometimes not used on EHCI/UHCI/OHCI 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, 27 May 2007 20:35:59 -0000 Hi, I've got some reports back that some USB host controllers do not support transferring memory from a location higher than 2GB. What should we do about this? Should we limit all USB DMA allocations to the lower 2GB of the memory? --HPS From owner-freebsd-usb@FreeBSD.ORG Sun May 27 20:55:51 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9B6E16A421 for ; Sun, 27 May 2007 20:55:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 7984E13C448 for ; Sun, 27 May 2007 20:55:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4RKrseW003715; Sun, 27 May 2007 14:53:54 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 27 May 2007 14:54:12 -0600 (MDT) Message-Id: <20070527.145412.-1597331197.imp@bsdimp.com> To: hselasky@c2i.net From: "M. Warner Losh" In-Reply-To: <200705272235.46048.hselasky@c2i.net> References: <200705272235.46048.hselasky@c2i.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 27 May 2007 14:53:54 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI 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, 27 May 2007 20:55:51 -0000 In message: <200705272235.46048.hselasky@c2i.net> Hans Petter Selasky writes: : I've got some reports back that some USB host controllers do not support : transferring memory from a location higher than 2GB. : : What should we do about this? : : Should we limit all USB DMA allocations to the lower 2GB of the memory? busdma should be managing this behind the scenes. You shouldn't care, as the problematical usb controllers, if any, can do the bouncing as required. We need to get the hierarchical bus tagging stuff more fully integrated, then we'd get this for free. Of course, you'd have to stop using contigmalloc to allocate all the memory for usb. That won't work on some of the embedded platforms we have, for example, because memory on them isn't as fungible as it is on i386 and amd64. Warner From owner-freebsd-usb@FreeBSD.ORG Sun May 27 21:40:14 2007 Return-Path: X-Original-To: freebsd-usb@hub.freebsd.org Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22D3116A46B for ; Sun, 27 May 2007 21:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 12C4113C484 for ; Sun, 27 May 2007 21:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4RLeD99070409 for ; Sun, 27 May 2007 21:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4RLeD9b070408; Sun, 27 May 2007 21:40:13 GMT (envelope-from gnats) Date: Sun, 27 May 2007 21:40:13 GMT Message-Id: <200705272140.l4RLeD9b070408@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Hans Petter Selasky Cc: Subject: Re: usb/113060: Samsung printer not working in bidirectional mode X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hans Petter Selasky List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2007 21:40:14 -0000 The following reply was made to PR usb/113060; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Ulrich Spoerlein , FreeBSD-gnats-submit@freebsd.org Subject: Re: usb/113060: Samsung printer not working in bidirectional mode Date: Sun, 27 May 2007 22:32:32 +0200 On Sunday 27 May 2007 17:33, Ulrich Spoerlein wrote: > >Number: 113060 > >Category: usb > >Synopsis: Samsung printer not working in bidirectional mode > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sun May 27 15:40:04 GMT 2007 > >Closed-Date: > >Last-Modified: > >Originator: Ulrich Sp=F6rlein > >Release: FreeBSD 6.2-STABLE i386 > >Organization: > >Environment: > >Description: > > The following printer, when attached via USB fails to work > > port 2 addr 2: full speed, self powered, config 1, SAMSUNG Laser Printer > ML-4600(0x3004), SAMSUNG ELECTRONICS CO., LT(0x04e8), rev 1.00 > > Peter van Heusden identified the problem to be the bi-directional mode. > When adding the quirks as given below *OR* chmod a-w /dev/ulpt0 CUPS will > print just fine. > > Please note that under the new USB stack developed by Hans Petter Selasky > the printer works out of the box. This, and usb/112944 leave me to believe > it is a more general problem with bidirectional support under ulpt(4). > > Perhaps HPS can comment on the architectural differences between the old > and his new ulpt(4)? > > PS: Whitespace and sorting in usb_quirks.c are, well, interessting. > > >How-To-Repeat: > >Fix: > > --- ml4600.diff begins here --- > Index: usb_quirks.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/dev/usb/usb_quirks.c,v > retrieving revision 1.41.2.8 > diff -u -p -r1.41.2.8 usb_quirks.c > --- usb_quirks.c 28 Apr 2007 20:31:30 -0000 1.41.2.8 > +++ usb_quirks.c 27 May 2007 15:31:37 -0000 > @@ -99,6 +99,7 @@ Static const struct usbd_quirk_entry { > { USB_VENDOR_HP, USB_PRODUCT_HP_810C, ANY, { UQ_BROKEN_BIDIR }}, > { USB_VENDOR_HP, USB_PRODUCT_HP_830C, ANY, { UQ_BROKEN_BIDIR }}, > { USB_VENDOR_HP, USB_PRODUCT_HP_1220C, ANY, { UQ_BROKEN_BIDIR }}, > + { USB_VENDOR_SAMSUNG, USB_PRODUCT_SAMSUNG_ML4600, ANY, { > UQ_BROKEN_BIDIR }}, { USB_VENDOR_XEROX, USB_PRODUCT_XEROX_WCM15, ANY,= =20 > { UQ_BROKEN_BIDIR }}, /* YAMAHA router's ucdDevice is the version of > farmware and often changes. */ { USB_VENDOR_YAMAHA, > USB_PRODUCT_YAMAHA_RTA54I, > Index: usbdevs > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/dev/usb/usbdevs,v > retrieving revision 1.232.2.24 > diff -u -p -r1.232.2.24 usbdevs > --- usbdevs 20 May 2007 12:34:39 -0000 1.232.2.24 > +++ usbdevs 27 May 2007 09:30:30 -0000 > @@ -1491,6 +1491,7 @@ product RATOC REXUSB60 0xb000 REX-USB60 > product SAGEM USBSERIAL 0x0027 USB-Serial Controller > > /* Samsung products */ > +product SAMSUNG ML4600 0x3004 ML-4600 laser printer > product SAMSUNG ML6060 0x3008 ML-6060 laser printer > > /* SanDisk products */ > --- ml4600.diff ends here --- > > >Release-Note: > >Audit-Trail: > >Unformatted: > Hi, The main difference between the old "ulpt" and the new "ulpt" is that the n= ew=20 use asynchronous reading of data, while the old "ulpt" uses synchronous=20 reading. That means that the new "ulpt" transfers data to/from all endpoint= s=20 in the background. Maybe that has something to do with the problem, that the IN enpoint is not= =20 polled. =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Sun May 27 22:19:41 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7484116A46E for ; Sun, 27 May 2007 22:19:41 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id 1E03513C487 for ; Sun, 27 May 2007 22:19:41 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (s82c7xfymco4jhfx@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l4RLrUj6021228; Sun, 27 May 2007 14:53:30 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l4RLrUWp021227; Sun, 27 May 2007 14:53:30 -0700 (PDT) (envelope-from jmg) Date: Sun, 27 May 2007 14:53:29 -0700 From: John-Mark Gurney To: Hans Petter Selasky Message-ID: <20070527215329.GY4602@funkthat.com> Mail-Followup-To: Hans Petter Selasky , freebsd-usb@freebsd.org References: <200705272235.46048.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705272235.46048.hselasky@c2i.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2007 22:19:41 -0000 Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: > I've got some reports back that some USB host controllers do not support > transferring memory from a location higher than 2GB. > > What should we do about this? > > Should we limit all USB DMA allocations to the lower 2GB of the memory? No, a quirk table should be setup and pass the restriction to bus_dma at tag initalization time when a broken controller is detected.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-usb@FreeBSD.ORG Sun May 27 22:40:06 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D53D016A4F0 for ; Sun, 27 May 2007 22:40:06 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id B297413C4BA for ; Sun, 27 May 2007 22:40:06 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org ([192.147.25.65]:56269) by thebighonker.lerctr.org with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1HsR8E-0001mE-SZ for freebsd-usb@freebsd.org; Sun, 27 May 2007 17:22:36 -0500 Date: Sun, 27 May 2007 17:22:32 -0500 (CDT) From: Larry Rosenman To: freebsd-usb@freebsd.org Message-ID: <20070527172140.E6790@thebighonker.lerctr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, DKIM_POLICY_SIGNSOME=0.001 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8, BAYES_00=-2.599, DKIM_POLICY_SIGNSOME=0.001 DomainKey-Status: no signature Subject: Re: USB Attach issues? (fwd) 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, 27 May 2007 22:40:06 -0000 Let me direct the below here as well, since someone might have more clue. Any help appreciated. I can also supply whatever else someone needs :) Thanks! LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ---------- Forwarded message ---------- Date: Sun, 27 May 2007 14:10:14 -0500 (CDT) From: Larry Rosenman To: freebsd-current@FreeBSD.org Subject: Re: USB Attach issues? On Sun, 27 May 2007, Larry Rosenman wrote: > I'm seeing the following: > > > usb2: root hub problem, error=4 > usb3: root hub problem, error=4 > > > In my Intel 5000 series chipset box. This is a SuperMicro SYS-7045B-TR+ > system. > > I've placed the following at http://www.lerctr.org/FreeBSD-CURRENT/ : Grr. Make that: http://www.lerctr.org/~ler/FreeBSD-CURRENT/ : > > -rw-r--r-- 1 ler ler 7156 May 27 13:58 BORG > -rw-r--r-- 1 ler ler 13911 May 27 14:01 borg.lerctr.org.asl.gz > -rw-r--r-- 1 ler ler 36124 May 27 13:58 dmesg.boot > > The BORG file is the kernel config, and dmesg.boot is a verbose boot. > > The borg.lerctr.org.asl.gz is the acpidump -td. > > I can give SSH access if that would help. > > Thanks all. > > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Mon May 28 06:43:58 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49DCC16A4FC for ; Mon, 28 May 2007 06:43:58 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 3D48913C44B for ; Mon, 28 May 2007 06:43:57 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe05.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 403537376; Mon, 28 May 2007 08:43:55 +0200 From: Hans Petter Selasky To: "M. Warner Losh" Date: Mon, 28 May 2007 08:43:45 +0200 User-Agent: KMail/1.9.5 References: <200705272235.46048.hselasky@c2i.net> <20070527.145412.-1597331197.imp@bsdimp.com> In-Reply-To: <20070527.145412.-1597331197.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705280843.45808.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI 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: Mon, 28 May 2007 06:43:58 -0000 On Sunday 27 May 2007 22:54, M. Warner Losh wrote: > In message: <200705272235.46048.hselasky@c2i.net> > > Hans Petter Selasky writes: > : I've got some reports back that some USB host controllers do not support > : transferring memory from a location higher than 2GB. > : > : What should we do about this? > : > : Should we limit all USB DMA allocations to the lower 2GB of the memory? > > busdma should be managing this behind the scenes. You shouldn't care, > as the problematical usb controllers, if any, can do the bouncing as > required. We need to get the hierarchical bus tagging stuff more > fully integrated, then we'd get this for free. Yes, I just changed the lowaddr when I allocated the tag, and that did the trick! > > Of course, you'd have to stop using contigmalloc to allocate all the > memory for usb. That won't work on some of the embedded platforms we > have, for example, because memory on them isn't as fungible as it is > on i386 and amd64. My new USB stack has been using "bus_dmamem" for quite a while. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon May 28 06:51:04 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 795F416A475 for ; Mon, 28 May 2007 06:51:04 +0000 (UTC) (envelope-from igorpopov@newmail.ru) Received: from mx1.mail.wbt.ru (mx1.mail.wbt.ru [80.250.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id 9F1AF13C483 for ; Mon, 28 May 2007 06:51:03 +0000 (UTC) (envelope-from igorpopov@newmail.ru) Received: from moon.wbt.ru ([80.250.66.38]) by mx1.mail.wbt.ru (Exim) with esmtp sent from id 1HsZ4G-000P0V-E8; Mon, 28 May 2007 09:51:00 +0300 From: Igor Popov Organization: Home To: Hans Petter Selasky Date: Mon, 28 May 2007 09:50:33 +0300 User-Agent: KMail/1.9.6 References: <200705061151.l46Bp4e9013742@www.freebsd.org> <200705080919.45417.igorpopov@newmail.ru> <200705132235.56792.hselasky@c2i.net> In-Reply-To: <200705132235.56792.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200705280950.34264.igorpopov@newmail.ru> X-ACL-Warn: X-AV 1 1180335060 X-ACL-Warn: X-AV 2 1180335060 X-ACL-Warn: X-AV 3 1180335060 X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release X-SpamTest-Info: Not protected Cc: freebsd-usb@freebsd.org Subject: Re: usb/112461: ehci USB 2.0 doesn't work on nforce4 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: Mon, 28 May 2007 06:51:04 -0000 =D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE=D1=82 = Sunday 13 May 2007 23:35:56 Hans Petter Selasky =D0=BD=D0=B0=D0=BF=D0=B8=D1= =81=D0=B0=D0=BB(=D0=B0): > On Tuesday 08 May 2007 08:19, Igor Popov wrote: > > =D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE=D1= =82 Monday 07 May 2007 16:12:50 Hans Petter Selasky =D0=BD=D0=B0=D0=BF=D0= =B8=D1=81=D0=B0=D0=BB(=D0=B0): > > > On Monday 07 May 2007 08:09, Igor Popov wrote: > > > > Good morning. > > > > > > > > > On Sunday 06 May 2007 13:51, Igor Popov wrote: > > > > > > >Number: 112461 > > > > > > >Category: usb > > > > > > >Synopsis: ehci USB 2.0 doesn't work on nforce4 > > > > > > >Confidential: no > > > > > > >Severity: non-critical > > > > > > >Priority: medium > > > > > > >Responsible: freebsd-usb > > > > > > >State: open > > > > > > >Quarter: > > > > > > >Keywords: > > > > > > >Date-Required: > > > > > > >Class: sw-bug > > > > > > >Submitter-Id: current-users > > > > > > >Arrival-Date: Sun May 06 12:00:11 GMT 2007 > > > > > > >Closed-Date: > > > > > > >Last-Modified: > > > > > > >Originator: Igor Popov > > > > > > >Release: 6.0, 6.1, 6.2 > > > > > > >Organization: > > > > > > >Environment: > > > > > > > > > > > > FreeBSD unix.my.net 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Sat Jan > > > > > > 27 13:01:18 EET 2007 > > > > > > toor@unix.my.net:/usr/obj/usr/src/sys/SUPERKERNEL i386 > > > > > > > > > > > > >Description: > > > > > > > > > > > > I have motherboard(Asus A8N-E) that built on nforce4 chipset, it > > > > > > has usb 2.0 ports, but under FreeBSD with usb 2.0 flashdrive max > > > > > > speed near 1.2Mb/s on file copying (my custom kernel has ehci > > > > > > driver), that is usb1.[01] speed. But under both linux an windo= ws > > > > > > with the same flashdrive speed is near 10Mb/s. > > > > > > > > > > > > Copyright (c) 1992-2007 The FreeBSD Project. > > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, > > > > > > 1993, 1994 The Regents of the University of California. All > > > > > > rights reserved. FreeBSD is a registered trademark of The FreeB= SD > > > > > > Foundation. FreeBSD 6.2-RELEASE #0: Sat Jan 27 13:01:18 EET 2007 > > > > > > toor@unix.my.net:/usr/obj/usr/src/sys/SUPERKERNEL > > > > > > ACPI APIC Table: > > > > > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > > > > > CPU: AMD Athlon(tm) 64 Processor 3000+ (1809.28-MHz 686-class > > > > > > CPU) Origin =3D "AuthenticAMD" Id =3D 0x20ff2 Stepping =3D 2 > > > > > > > > > > > > Features=3D0x78bfbff > > > > >RR ,P GE ,M CA ,CM OV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> > > > > > > Features2=3D0x1 > > > > > > AMD Features=3D0xe2500800 > > > > > > AMD Features2=3D0x1 > > > > > > real memory =3D 536805376 (511 MB) > > > > > > avail memory =3D 507523072 (484 MB) > > > > > > ioapic0 irqs 0-23 on motherboard > > > > > > wlan: mac acl policy registered > > > > > > ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, > > > > > > RF2413, RF5413) acpi0: on motherboard > > > > > > acpi_bus_number: can't get _ADR > > > > > > acpi_bus_number: can't get _ADR > > > > > > acpi0: Power Button (fixed) > > > > > > acpi_bus_number: can't get _ADR > > > > > > acpi_bus_number: can't get _ADR > > > > > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > > > > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on > > > > > > acpi0 cpu0: on acpi0 > > > > > > acpi_button0: on acpi0 > > > > > > pcib0: port 0xcf8-0xcff on acpi0 > > > > > > pci0: on pcib0 > > > > > > pci0: at device 0.0 (no driver attached) > > > > > > isab0: at device 1.0 on pci0 > > > > > > isa0: on isab0 > > > > > > nfsmb0: port > > > > > > 0xe400-0xe41f,0x4c00-0x4c3f,0x4c 40-0x4c7f irq 20 at device 1.1 > > > > > > on pci0 smbus0: on nfsmb0 > > > > > > smb0: on smbus0 > > > > > > nfsmb1: on nfsmb0 > > > > > > smbus1: on nfsmb1 > > > > > > smb1: on smbus1 > > > > > > ohci0: mem 0xd3104000-0xd3104fff > > > > > > irq 21 at devic e 2.0 on pci0 > > > > > > ohci0: [GIANT-LOCKED] > > > > > > usb0: OHCI version 1.0, legacy support > > > > > > usb0: on ohci0 > > > > > > usb0: USB revision 1.0 > > > > > > uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > > > > > uhub0: 10 ports with 10 removable, self powered > > > > > > ehci0: mem > > > > > > 0xfeb00000-0xfeb000ff irq 22 at d evice 2.1 on pci0 > > > > > > ehci0: [GIANT-LOCKED] > > > > > > usb1: EHCI version 1.0 > > > > > > usb1: companion controller, 4 ports each: usb0 > > > > > > usb1: on ehci0 > > > > > > usb1: USB revision 2.0 > > > > > > uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > > > > > > uhub1: 10 ports with 10 removable, self powered > > > > > > pcm0: port 0xdc00-0xdcff,0xe000-0xe0ff mem > > > > > > 0xd3103000-0xd3103ff f irq 23 at device 4.0 on pci0 > > > > > > pcm0: > > > > > > atapci0: port > > > > > > 0x1f0-0x1f7,0x3f6,0x170-0 x177,0x376,0xf000-0xf00f at device 6.0 > > > > > > on pci0 ata0: on atapci0 > > > > > > ata1: on atapci0 > > > > > > atapci1: port > > > > > > 0x9f0-0x9f7,0xbf0-0xbf3,0 x970-0x977,0xb70-0xb73,0xd800-0xd80f > > > > > > mem 0xd3102000-0xd3102fff irq 21 at device 7.0 on pci0 > > > > > > ata2: on atapci1 > > > > > > ata3: on atapci1 > > > > > > atapci2: port > > > > > > 0x9e0-0x9e7,0xbe0-0xbe3,0 x960-0x967,0xb60-0xb63,0xc400-0xc40f > > > > > > mem 0xd3101000-0xd3101fff irq 22 at device 8.0 on pci0 > > > > > > ata4: on atapci2 > > > > > > ata5: on atapci2 > > > > > > pcib1: at device 9.0 on pci0 > > > > > > pci5: on pcib1 > > > > > > ath0: mem 0xd3000000-0xd300ffff irq 16 at device > > > > > > 6.0 on pci5 ath0: Ethernet address: 00:15:e9:a4:58:9b > > > > > > ath0: mac 7.9 phy 4.5 radio 5.6 > > > > > > nfe0: port > > > > > > 0xb000-0xb007 mem 0xd3 100000-0xd3100fff irq 23 at device 10.0 = on > > > > > > pci0 > > > > > > miibus0: on nfe0 > > > > > > e1000phy0: on miibus0 > > > > > > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > > > > > > 1000baseTX-FDX, auto nfe0: Ethernet address: 00:17:31:13:8d:3f > > > > > > nfe0: [FAST] > > > > > > pcib2: at device 11.0 on pci0 > > > > > > pci4: on pcib2 > > > > > > pcib3: at device 12.0 on pci0 > > > > > > pci3: on pcib3 > > > > > > pcib4: at device 13.0 on pci0 > > > > > > pci2: on pcib4 > > > > > > pcib5: at device 14.0 on pci0 > > > > > > pci1: on pcib5 > > > > > > nvidia0: port 0xa000-0xa07f mem > > > > > > 0xd0000000-0xd0ffffff,0xc0 > > > > > > 000000-0xcfffffff,0xd1000000-0xd1ffffff irq 18 at device 0.0 on > > > > > > pci1 nvidia0: [GIANT-LOCKED] > > > > > > acpi_tz0: on acpi0 > > > > > > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq > > > > > > 2 on acpi0 fdc0: [FAST] > > > > > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > > > > > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags > > > > > > 0x10 on acpi0 sio0: type 16550A > > > > > > ppc0: port 0x378-0x37f irq 7 on > > > > > > acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > > > > > > ppbus0: on ppc0 > > > > > > lpt0: on ppbus0 > > > > > > lpt0: Interrupt-driven port > > > > > > ppi0: on ppbus0 > > > > > > atkbdc0: port 0x60,0x64 irq 1 on > > > > > > acpi0 atkbd0: irq 1 on atkbdc0 > > > > > > atkbd0: [GIANT-LOCKED] > > > > > > psm0: irq 12 on atkbdc0 > > > > > > psm0: [GIANT-LOCKED] > > > > > > psm0: model IntelliMouse, device ID 3 > > > > > > pmtimer0 on isa0 > > > > > > sc0: at flags 0x100 on isa0 > > > > > > sc0: VGA <16 virtual consoles, flags=3D0x300> > > > > > > sio1: configured irq 3 not in bitmap of probed irqs 0 > > > > > > sio1: port may not be enabled > > > > > > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbff= ff > > > > > > on isa0 Timecounter "TSC" frequency 1809282513 Hz quality 800 > > > > > > Timecounters tick every 1.000 msec > > > > > > ad0: 238475MB at ata0-master UDMA100 > > > > > > acd0: DVDR at ata1-master UDMA66 > > > > > > ad1: 190782MB at ata5-master SATA150 > > > > > > Trying to mount root from ufs:/dev/ad0s2a > > > > > > ath0: link state changed to UP > > > > > > nfe0: link state changed to UP > > > > > > umass0: vendor 0x0457 USB Mass Storage Device, rev 2.00/1.00, > > > > > > addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 > > > > > > da0: Removable Direct Access SCSI-2 > > > > > > device da0: 40.000MB/s transfers > > > > > > da0: 3920MB (8028160 512 byte sectors: 255H 63S/T 499C) > > > > > > > > > > This is maybe a SCSI problem. > > > > > > > > > > If you install the new USB stack [the SVN version], see: > > > > > > > > > > http://www.turbocat.net/~hselasky/usb4bsd > > > > > > > > > > Then try to copy some files and turn on debugging: > > > > > > > > > > sysctl hw.usb.umass.debug=3D-1 > > > > > > > > > > You might get a lot of messages. Look for errors. > > > > > > > > No, it is standard kernel from RELENG_6_2 branch, usb stack is not > > > > modified. > > > > > > You have to compile a new USB kernel with "options USB_DEBUG". My new > > > USB stack has that flag set by default. > > > > Recompiled kernel with makeoptions DEBUG=3D-DUSB_DEBUG > > # sysctl hw.usb > > hw.usb.ehci.debug: 1 > > hw.usb.ohci.debug: 1 > > hw.usb.ugen.debug: 1 > > hw.usb.uhci.debug: 1 > > hw.usb.uhci.loop: 0 > > hw.usb.uhid.debug: 0 > > hw.usb.uhub.debug: 0 > > hw.usb.ukbd.debug: 0 > > hw.usb.ulpt.debug: 0 > > hw.usb.umass.debug: 1 > > hw.usb.ums.debug: 0 > > hw.usb.debug: 1 > > > > ehci_pcd: change=3D0x02 > > ehci after reset, status=3D0x00001005 > > ehci port 1 reset, status =3D 0x00001005 > > usbd_new_device bus=3D0xc3b51000 port=3D1 depth=3D1 speed=3D3 > > usbd_new_device: adding unit addr=3D2, rev=3D200, class=3D0, subclass= =3D0, > > protocol=3D0, maxpacket=3D64, len=3D18, speed=3D3 > > usbd_new_device: new dev (addr 2), dev=3D0xc4c35900, parent=3D0xc3b3f900 > > usbd_probe_and_attach: trying device specific drivers > > usbd_probe_and_attach: no device specific driver found > > usbd_probe_and_attach: looping over 1 configurations > > usbd_set_config_index: (addr 1) cno=3D2 attr=3D0x80, selfpowered=3D0, p= ower=3D98 > > usbd_set_config_index: set config 1 > > umass0: vendor 0x0457 USB Mass Storage Device, rev 2.00/1.00, addr 2 > > umass0: SCSI over Bulk-Only; quirks =3D 0x0000 > > umass0:0:0:-1: Attached to scbus0 > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: Removable Direct Access SCSI-2 device > > da0: 40.000MB/s transfers > > da0: 3920MB (8028160 512 byte sectors: 255H 63S/T 499C) > > umass0: BBB reset failed, IOERROR > > ehci_device_clear_toggle: epipe=3D0xc4c35180 status=3D0x80008d00 > > usbd_dump_pipe: pipe=3D0xc4c35180 > > usbd_dump_iface: iface=3D0xc40bb020 > > device=3D0xc4c35900 idesc=3D0xc433fe09 index=3D0 altindex=3D0 priv=3D0 > > usbd_dump_device: dev=3D0xc4c35900 > > bus=3D0xc3b51000 default_pipe=3D0xc4c35800 > > address=3D2 config=3D1 depth=3D1 speed=3D3 self_powered=3D0 power=3D98 = langid=3D1033 > > usbd_dump_endpoint: endp=3D0xc3d12dcc > > edesc=3D0xc433fe19 refcnt=3D1 > > bEndpointAddress=3D0x82 > > (usbd_dump_pipe:) > > refcnt=3D1 running=3D0 aborting=3D0 > > intrxfer=3D0, repeat=3D0, interval=3D-1 > > umass0: BBB bulk-in clear stall failed, IOERROR > > ehci_device_clear_toggle: epipe=3D0xc4c35000 status=3D0x801f8049 > > usbd_dump_pipe: pipe=3D0xc4c35000 > > usbd_dump_iface: iface=3D0xc40bb020 > > device=3D0xc4c35900 idesc=3D0xc433fe09 index=3D0 altindex=3D0 priv=3D0 > > usbd_dump_device: dev=3D0xc4c35900 > > bus=3D0xc3b51000 default_pipe=3D0xc4c35800 > > address=3D2 config=3D1 depth=3D1 speed=3D3 self_powered=3D0 power=3D98 = langid=3D1033 > > usbd_dump_endpoint: endp=3D0xc3d12dc0 > > edesc=3D0xc433fe12 refcnt=3D1 > > bEndpointAddress=3D0x01 > > (usbd_dump_pipe:) > > refcnt=3D1 running=3D0 aborting=3D0 > > intrxfer=3D0, repeat=3D0, interval=3D-1 > > umass0: BBB bulk-out clear stall failed, IOERROR > > umass0: BBB reset failed, IOERROR > > ehci_device_clear_toggle: epipe=3D0xc4c35180 status=3D0x8d00 > > usbd_dump_pipe: pipe=3D0xc4c35180 > > usbd_dump_iface: iface=3D0xc40bb020 > > device=3D0xc4c35900 idesc=3D0xc433fe09 index=3D0 altindex=3D0 priv=3D0 > > usbd_dump_device: dev=3D0xc4c35900 > > bus=3D0xc3b51000 default_pipe=3D0xc4c35800 > > address=3D2 config=3D1 depth=3D1 speed=3D3 self_powered=3D0 power=3D98 = langid=3D1033 > > usbd_dump_endpoint: endp=3D0xc3d12dcc > > edesc=3D0xc433fe19 refcnt=3D1 > > bEndpointAddress=3D0x82 > > (usbd_dump_pipe:) > > refcnt=3D1 running=3D0 aborting=3D0 > > > > IOERROR on mount, so I have to turn of debug, unplug and plug usbdrive, > > mount it and turn on debug. On file copying there were no kernel > > messages. > > It looks like your UMASS device does not like to be started with a BBB > reset command. Is it possible for you to try out the new USB stack? > > --HPS I have recompiled kernel with new USB stack, now on files copying speed is= =20 about 3.8Mb/s, but it is still slower than linux or windows (~10Mb/s), may = be=20 it is by debug options in usb code. =2D-=20 "We've got a problem, HAL". "What kind of problem, Dave?" "A marketing problem. The Model 9000 isn't going anywhere. We're way short of our sales goals for fiscal 2010." "That can't be, Dave. The HAL Model 9000 is the world's most advanced Heuristically programmed ALgorithmic computer." "I know, HAL. I wrote the data sheet, remember? But the fact is, they're not selling." "Please explain, Dave. Why aren't HALs selling?" Bowman hesitates. "You aren't IBM compatible." [...] "The letters H, A, and L are alphabetically adjacent to the letters I, B, and M. That is as IBM compatible as I can be." "Not quite, HAL. The engineers have figured out a kludge." "What kludge is that, Dave?" "I'm going to disconnect your brain." -- Darryl Rubin, "A Problem in the Making", "InfoWorld" From owner-freebsd-usb@FreeBSD.ORG Mon May 28 06:53:30 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 862E516A47E for ; Mon, 28 May 2007 06:53:30 +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 23C3F13C45E for ; Mon, 28 May 2007 06:53:29 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe02.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 505682896; Mon, 28 May 2007 08:53:28 +0200 From: Hans Petter Selasky To: John-Mark Gurney Date: Mon, 28 May 2007 08:53:18 +0200 User-Agent: KMail/1.9.5 References: <200705272235.46048.hselasky@c2i.net> <20070527215329.GY4602@funkthat.com> In-Reply-To: <20070527215329.GY4602@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705280853.18551.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI 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: Mon, 28 May 2007 06:53:30 -0000 On Sunday 27 May 2007 23:53, John-Mark Gurney wrote: > Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: > > I've got some reports back that some USB host controllers do not support > > transferring memory from a location higher than 2GB. > > > > What should we do about this? > > > > Should we limit all USB DMA allocations to the lower 2GB of the memory? > > No, a quirk table should be setup and pass the restriction to bus_dma > at tag initalization time when a broken controller is detected.. Yes, I can do that. But I am also thinking about a static quirk, like a sysctl you can set at boot time. I hope that this is not a wide-spread problem. And I am not surprised that hardware manufacturers are not specification compliant, which really makes me wonder if they support a true 64-bit address bus on the EHCI controller at all. I would maybe cost too much money? And therefore we should just stick with 32-bit addressing on 32-bit platforms aswell. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon May 28 07:02:38 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8640816A46E for ; Mon, 28 May 2007 07:02:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id 1FC1613C455 for ; Mon, 28 May 2007 07:02:37 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe06.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 503751209; Mon, 28 May 2007 09:02:36 +0200 From: Hans Petter Selasky To: Igor Popov Date: Mon, 28 May 2007 09:02:27 +0200 User-Agent: KMail/1.9.5 References: <200705061151.l46Bp4e9013742@www.freebsd.org> <200705132235.56792.hselasky@c2i.net> <200705280950.34264.igorpopov@newmail.ru> In-Reply-To: <200705280950.34264.igorpopov@newmail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200705280902.27120.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: usb/112461: ehci USB 2.0 doesn't work on nforce4 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: Mon, 28 May 2007 07:02:38 -0000 On Monday 28 May 2007 08:50, Igor Popov wrote: > =D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE=D1= =82 Sunday 13 May 2007 23:35:56 Hans Petter Selasky =D0=BD=D0=B0=D0=BF=D0= =B8=D1=81=D0=B0=D0=BB(=D0=B0): > > On Tuesday 08 May 2007 08:19, Igor Popov wrote: > > > =D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE= =D1=82 Monday 07 May 2007 16:12:50 Hans Petter Selasky=20 =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0): > > > > On Monday 07 May 2007 08:09, Igor Popov wrote: > > > > > Good morning. > > > > > > > > > > > On Sunday 06 May 2007 13:51, Igor Popov wrote: Hi, > > I have recompiled kernel with new USB stack, now on files copying speed is > about 3.8Mb/s, but it is still slower than linux or windows (~10Mb/s), may > be it is by debug options in usb code. Could you supply some more details: How much ram has your system got? What filesystem is on your disks? What version of FreeBSD are you using? What is the dmesg when you boot? Hint: Simply run the "dmesg" command and p= ipe=20 the output to a file. =2D-HPS From owner-freebsd-usb@FreeBSD.ORG Mon May 28 07:04:59 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 51A2E16A4A1 for ; Mon, 28 May 2007 07:04:59 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id E238813C45B for ; Mon, 28 May 2007 07:04:58 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe03.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 510541831; Mon, 28 May 2007 09:04:57 +0200 From: Hans Petter Selasky To: Julian Elischer Date: Mon, 28 May 2007 09:04:46 +0200 User-Agent: KMail/1.9.5 References: <200705272235.46048.hselasky@c2i.net> <200705280853.18551.hselasky@c2i.net> <465A7E4A.10209@elischer.org> In-Reply-To: <465A7E4A.10209@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705280904.46850.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI 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: Mon, 28 May 2007 07:04:59 -0000 On Monday 28 May 2007 09:01, Julian Elischer wrote: > Hans Petter Selasky wrote: > > On Sunday 27 May 2007 23:53, John-Mark Gurney wrote: > >> Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: > >>> I've got some reports back that some USB host controllers do not > >>> support transferring memory from a location higher than 2GB. > >>> > >>> What should we do about this? > >>> > >>> Should we limit all USB DMA allocations to the lower 2GB of the memory? > >> > >> No, a quirk table should be setup and pass the restriction to bus_dma > >> at tag initalization time when a broken controller is detected.. > > > > Yes, I can do that. But I am also thinking about a static quirk, like a > > sysctl you can set at boot time. > > > > I hope that this is not a wide-spread problem. > > What manufacturers are we talking about here? and is there any possibility > that it's not the USB chipset, but rather, some feature of an intermediary > bus? Yes, that might be possible. I have asked the person that found the problem to send me his output from "pciconf -l -v". I will forward it to the USB list for discussion. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon May 28 07:15:52 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9557A16A46F for ; Mon, 28 May 2007 07:15:52 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outD.internet-mail-service.net (outD.internet-mail-service.net [216.240.47.227]) by mx1.freebsd.org (Postfix) with ESMTP id 813B113C4B9 for ; Mon, 28 May 2007 07:15:52 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 00:01:20 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id B0C50125A27; Mon, 28 May 2007 00:01:19 -0700 (PDT) Message-ID: <465A7E4A.10209@elischer.org> Date: Mon, 28 May 2007 00:01:30 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Hans Petter Selasky References: <200705272235.46048.hselasky@c2i.net> <20070527215329.GY4602@funkthat.com> <200705280853.18551.hselasky@c2i.net> In-Reply-To: <200705280853.18551.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI 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: Mon, 28 May 2007 07:15:52 -0000 Hans Petter Selasky wrote: > On Sunday 27 May 2007 23:53, John-Mark Gurney wrote: >> Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: >>> I've got some reports back that some USB host controllers do not support >>> transferring memory from a location higher than 2GB. >>> >>> What should we do about this? >>> >>> Should we limit all USB DMA allocations to the lower 2GB of the memory? >> No, a quirk table should be setup and pass the restriction to bus_dma >> at tag initalization time when a broken controller is detected.. > > Yes, I can do that. But I am also thinking about a static quirk, like a sysctl > you can set at boot time. > > I hope that this is not a wide-spread problem. What manufacturers are we talking about here? and is there any possibility that it's not the USB chipset, but rather, some feature of an intermediary bus? > > And I am not surprised that hardware manufacturers are not specification > compliant, which really makes me wonder if they support a true 64-bit address > bus on the EHCI controller at all. I would maybe cost too much money? And > therefore we should just stick with 32-bit addressing on 32-bit platforms > aswell. > > --HPS > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Mon May 28 07:50:31 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1276216A46E for ; Mon, 28 May 2007 07:50:31 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id 8FD5213C48C for ; Mon, 28 May 2007 07:50:30 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (oa4ci1z7g96s5r6e@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l4S7oMn8047918; Mon, 28 May 2007 00:50:22 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l4S7oMEm047916; Mon, 28 May 2007 00:50:22 -0700 (PDT) (envelope-from jmg) Date: Mon, 28 May 2007 00:50:22 -0700 From: John-Mark Gurney To: Hans Petter Selasky Message-ID: <20070528075022.GZ4602@funkthat.com> Mail-Followup-To: Hans Petter Selasky , freebsd-usb@freebsd.org References: <200705272235.46048.hselasky@c2i.net> <20070527215329.GY4602@funkthat.com> <200705280853.18551.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705280853.18551.hselasky@c2i.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-usb@freebsd.org Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 07:50:31 -0000 Hans Petter Selasky wrote this message on Mon, May 28, 2007 at 08:53 +0200: > On Sunday 27 May 2007 23:53, John-Mark Gurney wrote: > > Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: > > > I've got some reports back that some USB host controllers do not support > > > transferring memory from a location higher than 2GB. > > > > > > What should we do about this? > > > > > > Should we limit all USB DMA allocations to the lower 2GB of the memory? > > > > No, a quirk table should be setup and pass the restriction to bus_dma > > at tag initalization time when a broken controller is detected.. > > Yes, I can do that. But I am also thinking about a static quirk, like a sysctl > you can set at boot time. The only issue w/ this is that it would also effect add in USB PCI cards that aren't effected by the bug... Which means a sysctl would limit the hardware to the lowest common denominator... > I hope that this is not a wide-spread problem. > > And I am not surprised that hardware manufacturers are not specification > compliant, which really makes me wonder if they support a true 64-bit address > bus on the EHCI controller at all. I would maybe cost too much money? And > therefore we should just stick with 32-bit addressing on 32-bit platforms > aswell. Don't forget we have PAE for i386... so restricting to 32bit addressing for i386 would have an impact... As for it being an intermediate bus being the issue, I'd be surprised as that would mean that pci bridge to the USB controller is seriously broken... At least dealing w/ a intermediate bus is easier now that was have bus_get_dma_tag... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-usb@FreeBSD.ORG Mon May 28 07:59:34 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A739816A46B for ; Mon, 28 May 2007 07:59:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outK.internet-mail-service.net (outK.internet-mail-service.net [216.240.47.234]) by mx1.freebsd.org (Postfix) with ESMTP id 932E913C484 for ; Mon, 28 May 2007 07:59:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 00:59:34 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id D6300125A25; Mon, 28 May 2007 00:59:33 -0700 (PDT) Message-ID: <465A8BF0.6050808@elischer.org> Date: Mon, 28 May 2007 00:59:44 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Hans Petter Selasky , freebsd-usb@freebsd.org References: <200705272235.46048.hselasky@c2i.net> <20070527215329.GY4602@funkthat.com> <200705280853.18551.hselasky@c2i.net> <20070528075022.GZ4602@funkthat.com> In-Reply-To: <20070528075022.GZ4602@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 31st address line sometimes not used on EHCI/UHCI/OHCI 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: Mon, 28 May 2007 07:59:34 -0000 John-Mark Gurney wrote: > Hans Petter Selasky wrote this message on Mon, May 28, 2007 at 08:53 +0200: >> On Sunday 27 May 2007 23:53, John-Mark Gurney wrote: >>> Hans Petter Selasky wrote this message on Sun, May 27, 2007 at 22:35 +0200: >>>> I've got some reports back that some USB host controllers do not support >>>> transferring memory from a location higher than 2GB. >>>> >>>> What should we do about this? >>>> >>>> Should we limit all USB DMA allocations to the lower 2GB of the memory? >>> No, a quirk table should be setup and pass the restriction to bus_dma >>> at tag initalization time when a broken controller is detected.. >> Yes, I can do that. But I am also thinking about a static quirk, like a sysctl >> you can set at boot time. > > The only issue w/ this is that it would also effect add in USB PCI cards > that aren't effected by the bug... Which means a sysctl would limit the > hardware to the lowest common denominator... > >> I hope that this is not a wide-spread problem. >> >> And I am not surprised that hardware manufacturers are not specification >> compliant, which really makes me wonder if they support a true 64-bit address >> bus on the EHCI controller at all. I would maybe cost too much money? And >> therefore we should just stick with 32-bit addressing on 32-bit platforms >> aswell. > > Don't forget we have PAE for i386... so restricting to 32bit addressing > for i386 would have an impact... > > As for it being an intermediate bus being the issue, I'd be surprised > as that would mean that pci bridge to the USB controller is seriously > broken... At least dealing w/ a intermediate bus is easier now that > was have bus_get_dma_tag... > I'd rather it were a screwed up MB than a screwed up chip :-) From owner-freebsd-usb@FreeBSD.ORG Mon May 28 10:06:54 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D3F3316A47B for ; Mon, 28 May 2007 10:06:54 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id 75C8613C480 for ; Mon, 28 May 2007 10:06:54 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 209.67.61.254 with SMTP; 28 May 2007 09:40:12 -0000 Date: Mon, 28 May 2007 12:39:45 +0300 From: Nikolay Pavlov To: freebsd-usb@freebsd.org, freebsd-mobile@freebsd.org Message-ID: <20070528093944.GA12606@zone3000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: quetzal@zone3000.net Subject: ucom0: could not set data multiplex mode 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: Mon, 28 May 2007 10:06:54 -0000 Hi folks. I have an issue with CCU-550 CDMA modem (http://www.cmotech.com/eproduct6-1.htm) on recent current. Every time i am reattaching it i see this error: ucom0: could not set data multiplex mode So in order to work with it i have to reboot after each detache procedure. The only known workaround for this is to delete the "goto bad;" code in /usr/src/sys/dev/usb/umodem.c: printf("%s: could not set data multiplex mode\n", devname); goto bad; Could someone comment on this? P.S. Please cc me, becuase i am not subscribe to freebsd-usb or freebsd-mobile -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-usb@FreeBSD.ORG Mon May 28 11:08:48 2007 Return-Path: X-Original-To: freebsd-usb@FreeBSD.org Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7A0E16A485 for ; Mon, 28 May 2007 11:08:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id A6B4213C447 for ; Mon, 28 May 2007 11:08:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4SB8mjt068664 for ; Mon, 28 May 2007 11:08:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4SB8l9n068660 for freebsd-usb@FreeBSD.org; Mon, 28 May 2007 11:08:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 May 2007 11:08:47 GMT Message-Id: <200705281108.l4SB8l9n068660@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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: Mon, 28 May 2007 11:08:48 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_fs on externa o usb/91629 usb usbd_abort_pipe() may result in infinite loop 2 problems total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/40792 usb signals lead to data loss on device ugen o usb/46176 usb [panic] umass causes kernel panic if device removed be o i386/46371 usb USB controller cannot be initialized on IBM Netfinity f usb/55555 usb [ums] system freezes with access to /dev/ums0 o bin/57255 usb usbd and multi-function devices o usb/62088 usb [usb] Logitech Cordless/Optical Mouse not working o usb/62309 usb [ugen] [panic] panic: ugen(4) driver o usb/63621 usb [usb] USB MemoryStick Reader stalls/crashes system o usb/69006 usb [patch] Apple Cinema Display hangs USB ports o usb/71155 usb [usb] misbehaving usb-printer hangs processes, causes o usb/73307 usb [panic] Kernel panics on USB disconnect o usb/74771 usb [umass] mounting write-protected umass device as read/ o usb/75705 usb [panic] da0 attach / Optio S4 (with backtrace) o usb/75797 usb 5.3-STABLE(2005 1/4) detect USB headset, But can not f f usb/76204 usb panic while using usb attached modem o usb/76395 usb USB printer does not work, usbdevs says "addr 0 should o usb/77184 usb kernel panic on USB device disconnect o usb/77294 usb ucom + ulpcom panic o usb/77940 usb [quirk] [patch] insertion of usb keyboard panics syste f i386/78218 usb [kue] kue not detected on Sony PCG-F370 VAIO o usb/78989 usb please add USB keyboard support to install CD's o usb/79140 usb WD Firewire/USB Combo hangs under load on USB interfac o usb/79269 usb USB ohci da0 plug/unplug causes crashes and lockups. o usb/79287 usb UHCI hang after interrupt transfer o usb/79524 usb printing to Minolta PagePro 1[23]xxW via USB fails wit f usb/79656 usb [usb] RHSC interrupts lost o usb/79722 usb [usb] wrong alignments in ehci.h o usb/80040 usb [hang] Use of sound mixer causes system freeze with ua f usb/80260 usb Travan USB tape drive fails to write o usb/80361 usb mounting of usb-stick fails o usb/80829 usb possible panic when loading USB-modules o usb/80862 usb [patch] USB locking issues: missing some Giant calls o usb/81308 usb [ugen] [patch] polling a ugen(4) control endpoint caus f usb/82198 usb Panic on attaching of ONKI N-338 USB MP3 player f usb/82272 usb Can not recognize Casio camera EX-Z40 as a umass devic o usb/82350 usb [usb] null pointer dereference in USB stack o usb/82520 usb Reboot when USL101 connected s usb/82569 usb [usb] USB mass storage plug/unplug causes system panic o usb/82660 usb EHCI: I/O stuck in state 'physrd'/panic o usb/83504 usb [usb] SpeedTouch USB stop working on recent current (a o usb/83563 usb [panic] Page Fault while detaching Mpman Usb device o usb/83677 usb [usb] usb controller often not detected (Sun W2100z) o usb/83756 usb Microsoft Intellimouse Explorer 4.0A doesn't work. o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/84326 usb [umass] Panic trying to connect SCSI tape drive via US o usb/84336 usb [usb] [reboot] instant system reboot when unmounting a o usb/84936 usb install - usb keyboard not recognized o usb/86031 usb need support usb nic rt2500 in my 5.4 STABLE o usb/86767 usb [usb] bogus "slice starts beyond end of the disk:..." o usb/87099 usb panic: ohci_add_done: addr 0x000d1bf0 not found o usb/88743 usb [hang] USB makes kernel hang at boot (regression in 6. o usb/88966 usb kldunload ucom.ko returns "Device busy" error. o usb/89003 usb LaCie Firewire drive not properly supported under 6.0 o usb/89954 usb [usb] USB Disk driver race condition? f usb/89997 usb [umass] [panic] panic on iPod mini detach o usb/90162 usb [usb] [patch] Add support for the MS Wireless USB Mous o usb/90700 usb Kernel panic on connect/mount/use umass device o usb/91238 usb USB tape unit fails to write a second tape file to the o usb/91263 usb [patch] USB quirk needed for Logitec USB Hard disk LHD o usb/91283 usb booting very slow with usb devices connection (regress o usb/91538 usb Unable to print to EPSON CX3500 o usb/91906 usb FreeBSD hangs while booting with USB legacy support on o usb/92052 usb usbd causes defunct process with busy file-handle o kern/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92142 usb SET_ADDR_FAILED and SHORT_XFER errors from usb drivers o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/93155 usb [ulpt] /dev/ulpt0: device busy, USB printer does not w o usb/93408 usb hw.acpi.cpu.cx_lowest=C3 on AMD Turion causes choppy m f usb/93496 usb USB2.0 umass stalls on VIA o usb/93640 usb device ehci causes interrupt storm on this MSI amd64 m o usb/93828 usb ohci causes panic on boot (HP Pavillion d4100e) o usb/94166 usb btx halted with a flashcard plugged o usb/94384 usb kernel panic with usb2 hardware o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94742 usb [umass] [patch] umass driver does not recognise YANO e o usb/94813 usb mounting write-protected umass device freezes computer o usb/94897 usb Kernel Panic when cleanly unmounting USB disk o usb/95131 usb Boot/setup process does not accept key strokes o usb/95348 usb USB keyboard unplug causes noise on screen o usb/95562 usb Write Stress in USB Mass drive cause: [vinvalbuf: dir o usb/95636 usb [boot] 5 minute delay at boot when using VT6205 based o usb/96120 usb USB mouse not always detected o usb/96224 usb [usb] mount_msdosfs cause page fault in syncer process o usb/96457 usb fatback on umass = reboot o usb/97286 usb MS Wireless Intellimouse Explorer 2.0 doesn't work o usb/99431 usb FreeBSD on MSI 6566E (Intel 845E motherboards) doesn't o usb/101096 usb [if_ural] USB WLAN occasionally causes kernel-panics d o usb/101752 usb [panic] 6.1-RELEASE kernel panic on usb device inserti o usb/102066 usb [ukbd] usb keyboard and multimedia keys don't work o usb/102096 usb /usr/sbin/usbd does not handle multiple devices in one o usb/103025 usb [usb] wrong detection of USB device for FreeBSD 6.1 an o usb/104292 usb system lockup on forced umount of usb-storage device o usb/104830 usb system crashes when copying data to umass devices o usb/105186 usb USB 2.0/ehci on FreeBSD 6.2-PRE/AMD64 crashes box o usb/106615 usb [uftdi] uftdi module does not automatically load with o usb/106648 usb [hang] USB Floppy on D1950 10 min Hang on Insert w/o F o usb/106832 usb USB HP printer is not detected by kernel when ACPI ena o usb/107101 usb [umass] [patch] Quirk for Denver MP3 player o usb/107248 usb [PATCH] scsi_da.c quirk for Cowon iAUDIO X5 MP3 player o usb/107446 usb [umass] umass problems (usb and fw disks) o usb/107827 usb [panic] ohci_add_done addr not found o usb/107848 usb problem with samsung flash o usb/107924 usb [patch] usbd(8) does not call detach o usb/108097 usb [usbgen] [patch] ADMtek 851X USB-to-LAN adapter o usb/108513 usb [umass] Creative MuVo TX FM fails in 6.2-RELEASE (regr o usb/109274 usb [usb] MCP55 USB Controller fails to attach in AMD64 Cu o usb/109397 usb [panic] on boot from USB flash o usb/110122 usb [ugen] [patch] usb_interrupt_read does not respect tim o usb/110856 usb [ugen] [patch] interrupt in msgs are truncated when bu o usb/110988 usb [umass] [patch] Handling of quirk IGNORE_RESIDUE is um o kern/111753 usb [uhid] Replicable system panic involving UHID driver o usb/112568 usb USB mode may wrong when mounting psp o usb/112631 usb Problem with SONY DSC-S80 camera o usb/112640 usb [usb] Kernel freezes when writing a file to an ex2fs f 114 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o conf/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem s usb/32653 usb Added patches to improve USB scanner supportOB o usb/40948 usb [usb] USB HP CDW8200 does not work f usb/41415 usb [usb] [patch] Some USB scanners cannot talk to uscanne o usb/48342 usb [PATCH] usbd dynamic device list. o kern/51958 usb [usb] [patch] update for urio driver o kern/52026 usb [usb] feature request: umass driver support for InSyst o usb/53025 usb [ugen] [patch] ugen does not allow O_NONBLOCK for inte o usb/56095 usb [usb] [patch] QUIRK: Apacer Pen Drive fails to work o kern/59698 usb [kbd] [patch] Rework of ukbd HID to AT code translatio f usb/60248 usb [patch] Problem with USB printer HP LaserJet 1300 o usb/61234 usb [usb] [patch] usbhidaction(1) doesn't support using an o kern/62257 usb [umass] card reader UCR-61S2B is only half-supported o usb/63837 usb [uhid] [patch] USB: hid_is_collection() only looks for o kern/65769 usb [usb] Call to tcflush(x, TCIFLUSH) stops input on usb- o kern/66547 usb [usb] Palm Tungsten T USB does not initialize correctl o usb/68232 usb [ugen] [patch] ugen(4) isochronous handling correction o usb/68412 usb [usb] [patch] QUIRK: Philips KEY013 USB MP3 player o usb/70523 usb [usb] [patch] umct sending/receiving wrong characters o usb/70942 usb [usb] Genius Wireless USB mouse: moused doesn't work c o usb/71416 usb [usb] Cryptoflex e-gate USB token (ugen0) detach is no o usb/71417 usb [usb] Cryptoflex e-gate USB token (ugen0) communicatio o usb/71455 usb [usb] Slow USB umass performance of 5.3 o usb/71605 usb [umass] [patch] umass doesn't recognize multiple slots o usb/72380 usb [usb] USB does not work [dual Celeron Abit] o usb/72732 usb [patch] Kyocera 7135 quirk. o usb/72733 usb Kyocera 7135 Palm OS connection problem. o usb/73056 usb [usb] Sun Microsystems Type 6 USB mouse not working in o usb/74211 usb USB flash drive causes CAM status 0x4 on 4.10Release f usb/74358 usb [umass] unplugging at boot time an umass device crashe o usb/74453 usb Q-lity CD-RW USB ECW-043 (ScanLogic SL11R chipset) doe o usb/74557 usb imation 500mb usb key can only be written halfway on f o usb/74609 usb [umodem] [patch] allowing cdma modems to work at full o usb/74849 usb [usbdevs] [patch] Samsung SPH-i500 does not attach pro o usb/74880 usb [usb] [patch] Samsung N400 cellphone/acm fails to atac o kern/75764 usb [umass] [patch] "umass0: Phase Error" - no device for o usb/75800 usb ucom1: init failed STALLED error in time of sync with o usb/75928 usb Cytronix SmartMedia card (SMC) reader has problems whe o usb/76461 usb [umass] disklabel of umass(4)-CAM(4)-da(4) not used by o usb/76732 usb Mouse problems with USB KVM Switch f usb/78371 usb Philips Wearable Audio Player (128) fails to attach f usb/78984 usb Creative MUVO umass failure o usb/79723 usb [usb] prepare for high speed isochronous transfers o usb/79725 usb [usb] [patch] USB device speed is not double-checked o usb/79893 usb [umass] [patch] new usbdevs/umass quirks derived from o usb/80010 usb [aue] [patch] add support for the AEI USB to LAN adapt f usb/80773 usb "usbd_get_string()" could have taken a length paramete o usb/80774 usb have "usbd_find_desc" in line with the other "usbd_fin o usb/80776 usb [udav] UDAV device driver shouldn't use usb_add_task o usb/80777 usb usb_rem_task() should wait for callback to complete? o usb/80854 usb suggestion for new iface-no-probe mechanism o usb/80935 usb uvisor.c is not work with CLIE TH55. f usb/81621 usb external hd hangs under load on ehci o usb/82436 usb [usbdevs] [patch] USL101 Host-to-Host bridge support o o usb/83022 usb ALI USB 2.0 EHCI Controller is not detected o usb/83863 usb Communication problem between opensc/openct via USB wi o usb/85067 usb Cannot attach ScanJet 4300C to usb device o usb/85992 usb [uhid] [patch] USB stops working when trying to read f o usb/86195 usb [usbdevs] [patch] allow USB Ethernet Adaptor "ELECOM L o usb/86298 usb Known good USB mouse won't work with correct settings o usb/86438 usb Fix for non-working iPod over USB is in NetBSD CVS o usb/87224 usb Cannot mount USB Zip750 o usb/87648 usb [mouse] Logitech USB-optical mouse problem. o usb/88408 usb [axe] axe0 read PHY failed o usb/88939 usb [usbdevs] [patch] Fix cheapy Myson USB-IDE adapter f usb/89087 usb usb external harddrive hangs with BBB reset failed, TI f usb/91191 usb HP LaserJet 1020 (USB printer) not recognized f usb/91516 usb [umass] umass0 problems, with Freecom Classic SL Hard o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91811 usb Compact Flash in HP Photosmart 2610 return " Medium n o usb/91896 usb Serial Number of USB Memory Sticks is not passed throu o usb/92306 usb [quirk] [patch] Support for iRiver U10 USB media playe o usb/92403 usb [uplcom] uplcom.c needs new entry for 4.00 revision of o usb/92852 usb Vertical scroll not working properly on A4Tech WOP-49 o usb/93389 usb Digital Camera Pentax S60 don't work o usb/93872 usb [patch] SCSI quirk required for ELTA 8061 OL USB memor o usb/94132 usb [patch] quirk for CENTURY EX35QUAT disk enclosure o usb/94148 usb [usbdevs] [patch] Make if_cdce work with ARM linux han o usb/94311 usb [ugen][PATCH] allow interrupt IN transactions to be af o usb/94439 usb [patch] Add support for JNC MP3 Player o usb/94946 usb [uhub] [patch] code dynamic status size for status cha o usb/95037 usb USB disk didnt recognized on hot-plug. o usb/95173 usb [usb] cannot mount external usb harddisk VIA Technolog o usb/95241 usb [patch] add USB ID for OEM Pharos 360 GPS o usb/95805 usb [patch] Add Support for Siemens ES75 modem o usb/96381 usb [patch] add a quirk table entry for a flash ram usb st p usb/96546 usb [usb] [patch] Add support (quirk) for EasyMP3 EM732X U o usb/96714 usb [usbdevs] [patch] Update uvisor to support the Fossil o usb/97175 usb USB cardreader hangs system o usb/97472 usb [patch] add support for Olympus C150,D390 o usb/98343 usb BBB reset failed errors with Creative Muvo MP3 player; o usb/99419 usb external usb harddrive slow to accept o usb/99538 usb [kbd] while using USB keyboard default params of atkbd o usb/100746 usb [kbd] system does not boot due to USB keyboard problem o usb/101757 usb [patch] uhid.4: correct structure field names to match o usb/101761 usb [patch] usb.h: increase maximal size of report descrip o usb/101775 usb [libusbhid] [patch] possible error in report descripto o usb/102678 usb [kbd] Dell PowerEdge DRAC5 USB Keyboard does not work o usb/102976 usb Casio Exilim Digital Camera cause panic o usb/103046 usb [ulpt] [patch] ulpt event driven I/O with select(2) an o usb/103289 usb USB 2.0 problems on AMD LX-800 CPU and CS-5536 chipset o usb/103418 usb [usb] [patch] usbhidctl: add ability to write output a o usb/103917 usb USB driver reports "Addr 0 should never happen" o usb/104290 usb [patch] quirk: TOSHIBA DVD-RAM drive (libretto DVD Doc o usb/104352 usb [ural] ural driver doesnt work o usb/104645 usb Rave C-201 MP3 player does not communicate o usb/105065 usb [sata] SATA - USB Bridge o usb/105361 usb [panic] Kernel panic during unmounting mass storage (C o usb/105518 usb [patch] epson perfection 3490 usb scanner def o usb/106041 usb FreeBSD does not recognise Mustek BearPaw 2400TA usb s o usb/106070 usb devd recognizes ucom, but ttyU is the device actually o usb/106462 usb [usbdevs] Motorola U6 PEBL not recognized by system vi o usb/106538 usb [patch] Can not burn DVD on Sony DRX-820UL external US o usb/106621 usb [usb] DLINK DUB-E100 support broken o usb/106861 usb [PATCH]: usbdevs update: Add product ACER Zeevo BT-500 o usb/107243 usb [patch] Apacer USB Flash Drive quirk o usb/107388 usb [PATCH] Add utoppy device from NetBSD o usb/107496 usb USB device problem on RELENG_6_2 (SHORT_XFER) (regress o usb/107526 usb [usbdevs] Patch to support the Crystalfontz CFA-635 20 p usb/107642 usb [patch] add Ralink Technology RT2501USB/RT2601USB chip o kern/107665 usb [usb] [patch] uscanner support for epson stylus DX5050 o usb/107701 usb usbd ignores "detach" o usb/107935 usb [uplcom] panic while accessing /dev/cuaU0 o usb/108056 usb [ohci] Mouse gets powered off during device probe when o usb/108344 usb [panic] kernel with atausb panics when unplugging USB o usb/108427 usb [patch] quirk: Samsung MP0402H o usb/108509 usb [hang] FreeBSD hang at startup after ehci0 detected (C o usb/108810 usb [patch] quirk for I/O Magic USB flash drive "Giga Bank o usb/110197 usb [umass] Sony PSP umass device does not detach from EHC o usb/110477 usb [usbdevs] [patch] add Benq 3300U/4300U support to Free o usb/110681 usb [ukbd][patch] multiple keys will be repeated o usb/110991 usb [patch] QUIRK: Super Top IDE DEVICE (depends on usb/11 o usb/110992 usb [uftdi] [patch] Add Tactrix Openport support in uftdi o usb/111710 usb [patch] [usb] add support for Option GlobeTrotter 3G+ o usb/112161 usb [usbdevs] [patch] Option N.V. Fusion UMTS Quad-GPRS o usb/112392 usb [usbdevs] [patch] Make Epson Perfection 3490 recognize o usb/112461 usb ehci USB 2.0 doesn't work on nforce4 o usb/112463 usb problem with Samsung USB DVD writer, libscg and FreeBS o usb/112944 usb [patch] Bi-directional access to HP LaserJet 1010 prin o usb/113060 usb Samsung printer not working in bidirectional mode 140 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon May 28 15:33:52 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 06B7E16A469 for ; Mon, 28 May 2007 15:33:52 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 17DC013C43E for ; Mon, 28 May 2007 15:33:50 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe05.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 404028381; Mon, 28 May 2007 17:33:49 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 28 May 2007 17:33:38 +0200 User-Agent: KMail/1.9.5 References: <20070528093944.GA12606@zone3000.net> In-Reply-To: <20070528093944.GA12606@zone3000.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705281733.38786.hselasky@c2i.net> Cc: Nikolay Pavlov , freebsd-mobile@freebsd.org Subject: Re: ucom0: could not set data multiplex mode 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: Mon, 28 May 2007 15:33:52 -0000 On Monday 28 May 2007 11:39, Nikolay Pavlov wrote: > Hi folks. > I have an issue with CCU-550 CDMA modem > (http://www.cmotech.com/eproduct6-1.htm) on recent current. > Every time i am reattaching it i see this error: > ucom0: could not set data multiplex mode > > So in order to work with it i have to reboot after each detache > procedure. The only known workaround for this is to delete the > "goto bad;" code in /usr/src/sys/dev/usb/umodem.c: > > printf("%s: could not set data multiplex mode\n", > devname); > goto bad; > > Could someone comment on this? > > P.S. Please cc me, becuase i am not subscribe to freebsd-usb or > freebsd-mobile I'm not sure if it will help, but there is a new USB stack that you can try: http://www.turbocat.net/~hselasky/usb4bsd Download the SVN version. I recommend installing on FreeBSD 6-stable, hence there is a small bug in the memory allocation code on FreeBSD 7-current, that will cause regular panics. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon May 28 16:52:24 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C071316A41F for ; Mon, 28 May 2007 16:52:24 +0000 (UTC) (envelope-from amuntz@cerbere3.com) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.freebsd.org (Postfix) with ESMTP id 893A713C483 for ; Mon, 28 May 2007 16:52:24 +0000 (UTC) (envelope-from amuntz@cerbere3.com) Received: from Cerbere-de-Troyes.cerbere23.com (unknown [62.147.211.204]) by smtp1-g19.free.fr (Postfix) with ESMTP id 6F1001AB345 for ; Mon, 28 May 2007 18:52:23 +0200 (CEST) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.8/8.13.3) with ESMTP id l4SGqLQT002852 for ; Mon, 28 May 2007 18:52:22 +0200 (CEST) (envelope-from amuntz@cerbere3.com) From: "Aymeric MUNTZ \(Cerbere3\)" To: Date: Mon, 28 May 2007 18:52:29 +0200 Organization: Cerbere3 Message-ID: <000001c7a148$94c5d9a0$0202a8c0@artemis> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Subject: UMASS pbm at startup 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: Mon, 28 May 2007 16:52:24 -0000 Hi, I have a pbm with my usb disk-key under freebsd. When i start the system (FreeBSD 5.2) with the key already plugged, it = is not recognised. If I unplug and replug it, it is recognised. With an other motherboard, I do not have this problem. Is there a way to rescan for usb devices? I already tried "camcontrol = rescan all" with no success. Thanks Cheers Alex From owner-freebsd-usb@FreeBSD.ORG Mon May 28 17:12:43 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F76216A51D for ; Mon, 28 May 2007 17:12:43 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 3A2EC13C4BF for ; Mon, 28 May 2007 17:12:42 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe11.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 334751672; Mon, 28 May 2007 19:12:40 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 28 May 2007 19:12:30 +0200 User-Agent: KMail/1.9.5 References: <000001c7a148$94c5d9a0$0202a8c0@artemis> In-Reply-To: <000001c7a148$94c5d9a0$0202a8c0@artemis> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705281912.30389.hselasky@c2i.net> Cc: Subject: Re: UMASS pbm at startup 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: Mon, 28 May 2007 17:12:43 -0000 On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: > Hi, > > I have a pbm with my usb disk-key under freebsd. > When i start the system (FreeBSD 5.2) with the key already plugged, it is > not recognised. If I unplug and replug it, it is recognised. > With an other motherboard, I do not have this problem. > > Is there a way to rescan for usb devices? I already tried "camcontrol > rescan all" with no success. > Have you tried the SVN version of the new USB stack with FreeBSD 6.2 installed? --HPS PS: The new USB stack does not support FreeBSD 5.2 any more. http://www.turbocat.net/~hselasky/usb4bsd From owner-freebsd-usb@FreeBSD.ORG Mon May 28 17:57:21 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40C6616A468 for ; Mon, 28 May 2007 17:57:21 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id DB02613C45E for ; Mon, 28 May 2007 17:57:20 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4SHsAs3017947; Mon, 28 May 2007 11:54:10 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 11:54:26 -0600 (MDT) Message-Id: <20070528.115426.1723237052.imp@bsdimp.com> To: amuntz@cerbere3.com From: "M. Warner Losh" In-Reply-To: <000001c7a148$94c5d9a0$0202a8c0@artemis> References: <000001c7a148$94c5d9a0$0202a8c0@artemis> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 11:54:11 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: UMASS pbm at startup 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: Mon, 28 May 2007 17:57:21 -0000 In message: <000001c7a148$94c5d9a0$0202a8c0@artemis> "Aymeric MUNTZ \(Cerbere3\)" writes: : Is there a way to rescan for usb devices? I already tried "camcontrol rescan : all" with no success. Not presently in current, let alone 5.2. Maybe 6.2 would work better. Warner From owner-freebsd-usb@FreeBSD.ORG Mon May 28 18:02:00 2007 Return-Path: X-Original-To: freebsd-usb@FreeBSD.ORG Delivered-To: freebsd-usb@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CF11916A468 for ; Mon, 28 May 2007 18:02:00 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB6913C4C1 for ; Mon, 28 May 2007 18:02:00 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4SI1RMe018058; Mon, 28 May 2007 12:01:28 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 12:01:44 -0600 (MDT) Message-Id: <20070528.120144.-957833410.imp@bsdimp.com> To: hselasky@c2i.net From: "M. Warner Losh" In-Reply-To: <200705281912.30389.hselasky@c2i.net> References: <000001c7a148$94c5d9a0$0202a8c0@artemis> <200705281912.30389.hselasky@c2i.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 12:01:28 -0600 (MDT) Cc: freebsd-usb@FreeBSD.ORG Subject: Re: UMASS pbm at startup 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: Mon, 28 May 2007 18:02:00 -0000 In message: <200705281912.30389.hselasky@c2i.net> Hans Petter Selasky writes: : On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: : > Hi, : > : > I have a pbm with my usb disk-key under freebsd. : > When i start the system (FreeBSD 5.2) with the key already plugged, it is : > not recognised. If I unplug and replug it, it is recognised. : > With an other motherboard, I do not have this problem. : > : > Is there a way to rescan for usb devices? I already tried "camcontrol : > rescan all" with no success. : > : : Have you tried the SVN version of the new USB stack with FreeBSD 6.2 : installed? Let's just change one thing at a time... Try going to 6.2 first. changing both the usb stack and the freebsd version at one time might not be wise. We also need to track down problems in the current USB stack, since we are never going to put hps' stack into RELENG_6. Since it hasn't yet been committed to current and there's a freeze coming up shortly, it is doubtful that it will be in RELENG_7 either. We need to not view hps' stack as this magical thing that solves all problems because we have at least RELENG_6 to support for a while, and may have to support the current stack in RELENG_7 too. To be honest, I really wish Hans would be more pro-active in merging changes to the old stack so that the delta between it and his would be more manageable. I've said this plenty of times privately, but no fixes to the old stack have been forthcoming, not even new vendor IDs for existing drivers... Warner From owner-freebsd-usb@FreeBSD.ORG Mon May 28 18:05:19 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0381216A41F for ; Mon, 28 May 2007 18:05:19 +0000 (UTC) (envelope-from alexandre.delay@free.fr) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id BBA5913C4B9 for ; Mon, 28 May 2007 18:05:18 +0000 (UTC) (envelope-from alexandre.delay@free.fr) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by postfix2-g20.free.fr (Postfix) with ESMTP id 43EA4117DC99 for ; Mon, 28 May 2007 18:17:55 +0200 (CEST) Received: from Cerbere-de-Troyes.cerbere23.com (unknown [62.147.211.204]) by smtp1-g19.free.fr (Postfix) with ESMTP id 751491AB2BB for ; Mon, 28 May 2007 19:17:23 +0200 (CEST) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.8/8.13.3) with ESMTP id l4SHHMkY003208 for ; Mon, 28 May 2007 19:17:22 +0200 (CEST) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: Date: Mon, 28 May 2007 19:17:31 +0200 Message-ID: <000201c7a14c$132189e0$0202a8c0@artemis> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <200705281912.30389.hselasky@c2i.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Subject: RE : UMASS pbm at startup 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: Mon, 28 May 2007 18:05:19 -0000 I can not try this FBSD release. It is a server in production and I can = not reinstall it. I have to find the solution with the 5.2 FreeBSD version. -----Message d'origine----- De : owner-freebsd-usb@freebsd.org = [mailto:owner-freebsd-usb@freebsd.org] De la part de Hans Petter Selasky Envoy=E9 : lundi 28 mai 2007 19:13 =C0 : freebsd-usb@freebsd.org Objet : Re: UMASS pbm at startup On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: > Hi, > > I have a pbm with my usb disk-key under freebsd. > When i start the system (FreeBSD 5.2) with the key already plugged, it = > is not recognised. If I unplug and replug it, it is recognised. With=20 > an other motherboard, I do not have this problem. > > Is there a way to rescan for usb devices? I already tried "camcontrol=20 > rescan all" with no success. > Have you tried the SVN version of the new USB stack with FreeBSD 6.2=20 installed? --HPS PS: The new USB stack does not support FreeBSD 5.2 any more. http://www.turbocat.net/~hselasky/usb4bsd _______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Mon May 28 18:43:56 2007 Return-Path: X-Original-To: freebsd-usb@FreeBSD.ORG Delivered-To: freebsd-usb@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9242516A494 for ; Mon, 28 May 2007 18:43:56 +0000 (UTC) (envelope-from alexandre.delay@free.fr) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3435913C457 for ; Mon, 28 May 2007 18:43:56 +0000 (UTC) (envelope-from alexandre.delay@free.fr) Received: from Cerbere-de-Troyes.cerbere23.com (unknown [62.147.211.204]) by smtp1-g19.free.fr (Postfix) with ESMTP id 6880B1AB2E2; Mon, 28 May 2007 20:43:54 +0200 (CEST) Received: from artemis ([192.168.2.2]) by Cerbere-de-Troyes.cerbere23.com (8.13.8/8.13.3) with ESMTP id l4SIhrIT004317; Mon, 28 May 2007 20:43:53 +0200 (CEST) (envelope-from alexandre.delay@free.fr) From: "Alexandre DELAY" To: "'M. Warner Losh'" , Date: Mon, 28 May 2007 20:44:02 +0200 Message-ID: <000001c7a158$29592310$0202a8c0@artemis> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <20070528.120144.-957833410.imp@bsdimp.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Cc: freebsd-usb@FreeBSD.ORG Subject: RE : UMASS pbm at startup 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: Mon, 28 May 2007 18:43:56 -0000 But why does it work with an other motherboard and not with an other = one? It is the same usb mass storage and the same system. Is it possible that it = is due to IRQ interruptions? Maybe that the first motherboard doesn't have = IRQ on USB port!? Alex -----Message d'origine----- De : owner-freebsd-usb@freebsd.org = [mailto:owner-freebsd-usb@freebsd.org] De la part de M. Warner Losh Envoy=E9 : lundi 28 mai 2007 20:02 =C0 : hselasky@c2i.net Cc : freebsd-usb@FreeBSD.ORG Objet : Re: UMASS pbm at startup In message: <200705281912.30389.hselasky@c2i.net> Hans Petter Selasky writes: : On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: : > Hi, : > : > I have a pbm with my usb disk-key under freebsd. : > When i start the system (FreeBSD 5.2) with the key already plugged, = it is : > not recognised. If I unplug and replug it, it is recognised. : > With an other motherboard, I do not have this problem. : > : > Is there a way to rescan for usb devices? I already tried = "camcontrol : > rescan all" with no success. : > :=20 : Have you tried the SVN version of the new USB stack with FreeBSD 6.2=20 : installed? Let's just change one thing at a time... Try going to 6.2 first. = changing both the usb stack and the freebsd version at one time might not be = wise. We also need to track down problems in the current USB stack, since we = are never going to put hps' stack into RELENG_6. Since it hasn't yet been committed to current and there's a freeze coming up shortly, it is = doubtful that it will be in RELENG_7 either. We need to not view hps' stack as = this magical thing that solves all problems because we have at least RELENG_6 = to support for a while, and may have to support the current stack in = RELENG_7 too. To be honest, I really wish Hans would be more pro-active in merging = changes to the old stack so that the delta between it and his would be more manageable. I've said this plenty of times privately, but no fixes to = the old stack have been forthcoming, not even new vendor IDs for existing drivers... Warner _______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Mon May 28 19:29:06 2007 Return-Path: X-Original-To: freebsd-usb@FreeBSD.ORG Delivered-To: freebsd-usb@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4533E16A534 for ; Mon, 28 May 2007 19:29:06 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outF.internet-mail-service.net (outF.internet-mail-service.net [216.240.47.229]) by mx1.freebsd.org (Postfix) with ESMTP id 3135C13C45D for ; Mon, 28 May 2007 19:29:06 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 12:29:05 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 24F05125A24; Mon, 28 May 2007 12:29:05 -0700 (PDT) Message-ID: <465B2D8C.6050301@elischer.org> Date: Mon, 28 May 2007 12:29:16 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Alexandre DELAY References: <000001c7a158$29592310$0202a8c0@artemis> In-Reply-To: <000001c7a158$29592310$0202a8c0@artemis> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-usb@FreeBSD.ORG Subject: Re: RE : UMASS pbm at startup 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: Mon, 28 May 2007 19:29:06 -0000 Alexandre DELAY wrote: > But why does it work with an other motherboard and not with an other one? It > is the same usb mass storage and the same system. Is it possible that it is > due to IRQ interruptions? Maybe that the first motherboard doesn't have IRQ > on USB port!? > try a different USB port.. some motherboards do wierd things with some ports. > Alex > > -----Message d'origine----- > De : owner-freebsd-usb@freebsd.org [mailto:owner-freebsd-usb@freebsd.org] De > la part de M. Warner Losh > Envoyé : lundi 28 mai 2007 20:02 > À : hselasky@c2i.net > Cc : freebsd-usb@FreeBSD.ORG > Objet : Re: UMASS pbm at startup > > > In message: <200705281912.30389.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: > : > Hi, > : > > : > I have a pbm with my usb disk-key under freebsd. > : > When i start the system (FreeBSD 5.2) with the key already plugged, it > is > : > not recognised. If I unplug and replug it, it is recognised. > : > With an other motherboard, I do not have this problem. > : > > : > Is there a way to rescan for usb devices? I already tried "camcontrol > : > rescan all" with no success. > : > > : > : Have you tried the SVN version of the new USB stack with FreeBSD 6.2 > : installed? > > Let's just change one thing at a time... Try going to 6.2 first. changing > both the usb stack and the freebsd version at one time might not be wise. > We also need to track down problems in the current USB stack, since we are > never going to put hps' stack into RELENG_6. Since it hasn't yet been > committed to current and there's a freeze coming up shortly, it is doubtful > that it will be in RELENG_7 either. We need to not view hps' stack as this > magical thing that solves all problems because we have at least RELENG_6 to > support for a while, and may have to support the current stack in RELENG_7 > too. > > To be honest, I really wish Hans would be more pro-active in merging changes > to the old stack so that the delta between it and his would be more > manageable. I've said this plenty of times privately, but no fixes to the > old stack have been forthcoming, not even new vendor IDs for existing > drivers... > > Warner > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Mon May 28 19:36:13 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E454316A4FF for ; Mon, 28 May 2007 19:36:13 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 87C1813C4AE for ; Mon, 28 May 2007 19:36:13 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l4SJjbpE065302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 28 May 2007 15:45:45 -0400 (EDT) (envelope-from amistry@am-productions.biz) From: Anish Mistry Organization: AM Productions To: freebsd-usb@freebsd.org Date: Mon, 28 May 2007 15:18:40 -0400 User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1828985.LBhoRur5eA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200705281518.52086.amistry@am-productions.biz> X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_50,MYFREEBSD2, RCVD_IN_NJABL_DUL,SPF_SOFTFAIL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.7/3311/Sun May 27 20:21:25 2007 on mail.united-ware.com X-Virus-Status: Clean Subject: ETA on HPS USB stack into CURRENT? 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: Mon, 28 May 2007 19:36:14 -0000 --nextPart1828985.LBhoRur5eA Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline What requirements still need to be met before the HPS USB stack is=20 committed to CURRENT? I understand that introducing a major=20 sub-system change so close the start of a release cycle can be very=20 disruptive. My main concern is that the RELENG_7 branch will be=20 arriving in the next couple months and imp@ mentioned in the (Re:=20 UMASS pbm at startup) thread that RELENG_7 might not see the new=20 stack. This means that we'll have to wait until an 8.x release=20 (2009?) until we see the new stack in a stock install. Also the=20 current stack will then need to be supported during the entire life=20 of RELENG_7 which will probably into at least late 2010. From here on out the limitations of the current USB stack not being=20 MPSAFE will only become more apparent with more systems shipping with=20 multiple processors. Such as not allow CPUs to drop to C3 when USB=20 is loaded, performance issues, and various HID parsing problems. With all that said what would be needed so that we could see the new=20 stack in 7.1 eventhough 7.0 would have the old stack? Though this=20 does seem to be asking for a lot of trouble since it would be a=20 STABLE branch. =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart1828985.LBhoRur5eA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQBGWyscxqA5ziudZT0RAgfxAJ4/Js04Ei3dd4HD4pDoEjmiFlw89wCgpDcH g1aTkhtOfPN72eAVvGGY/w0= =tmNL -----END PGP SIGNATURE----- --nextPart1828985.LBhoRur5eA-- From owner-freebsd-usb@FreeBSD.ORG Mon May 28 20:20:06 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83BC016A421 for ; Mon, 28 May 2007 20:20:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2BF3813C483 for ; Mon, 28 May 2007 20:20:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4SKHDcw019240; Mon, 28 May 2007 14:17:13 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 14:17:29 -0600 (MDT) Message-Id: <20070528.141729.-1962670642.imp@bsdimp.com> To: amistry@am-productions.biz From: "M. Warner Losh" In-Reply-To: <200705281518.52086.amistry@am-productions.biz> References: <200705281518.52086.amistry@am-productions.biz> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 14:17:14 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: ETA on HPS USB stack into CURRENT? 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: Mon, 28 May 2007 20:20:06 -0000 In message: <200705281518.52086.amistry@am-productions.biz> Anish Mistry writes: : What requirements still need to be met before the HPS USB stack is : committed to CURRENT? It will go into the into the tree when it is ready. The FreeBSD project has a policy that all significant code must be reviewed before it goes into the tree, and that the concerns that have been raised in the review be addressed. This process is ongoing with the hps usb stack, and when it is complete, it will go into current. Warner From owner-freebsd-usb@FreeBSD.ORG Mon May 28 20:22:59 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB72C16A468 for ; Mon, 28 May 2007 20:22:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 7DB9913C468 for ; Mon, 28 May 2007 20:22:59 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4SKL6b9019280; Mon, 28 May 2007 14:21:07 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 14:21:23 -0600 (MDT) Message-Id: <20070528.142123.-749251258.imp@bsdimp.com> To: alexandre.delay@free.fr From: "M. Warner Losh" In-Reply-To: <000001c7a158$29592310$0202a8c0@artemis> References: <20070528.120144.-957833410.imp@bsdimp.com> <000001c7a158$29592310$0202a8c0@artemis> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 14:21:07 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: RE : UMASS pbm at startup 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: Mon, 28 May 2007 20:22:59 -0000 In message: <000001c7a158$29592310$0202a8c0@artemis> "Alexandre DELAY" writes: : But why does it work with an other motherboard and not with an other = one? It : is the same usb mass storage and the same system. Is it possible that= it is : due to IRQ interruptions? Maybe that the first motherboard doesn't ha= ve IRQ : on USB port!? The no IRQ is a big hint. Often times, usb is disabled by the BIOS by not assigning an interrupt to the controller. You might want to check to see if usb isn't disabled. Also, different motherboards have different chipsets, supported by different drivers. Warner : -----Message d'origine----- : De : owner-freebsd-usb@freebsd.org [mailto:owner-freebsd-usb@freebsd.= org] De : la part de M. Warner Losh : Envoy=E9 : lundi 28 mai 2007 20:02 : =C0 : hselasky@c2i.net : Cc : freebsd-usb@FreeBSD.ORG : Objet : Re: UMASS pbm at startup : = : = : In message: <200705281912.30389.hselasky@c2i.net> : Hans Petter Selasky writes: : : On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: : : > Hi, : : > : : > I have a pbm with my usb disk-key under freebsd. : : > When i start the system (FreeBSD 5.2) with the key already plugge= d, it : is : : > not recognised. If I unplug and replug it, it is recognised. : : > With an other motherboard, I do not have this problem. : : > : : > Is there a way to rescan for usb devices? I already tried "camcon= trol : : > rescan all" with no success. : : > : : = : : Have you tried the SVN version of the new USB stack with FreeBSD 6.= 2 = : : installed? : = : Let's just change one thing at a time... Try going to 6.2 first. cha= nging : both the usb stack and the freebsd version at one time might not be w= ise. : We also need to track down problems in the current USB stack, since w= e are : never going to put hps' stack into RELENG_6. Since it hasn't yet been= : committed to current and there's a freeze coming up shortly, it is do= ubtful : that it will be in RELENG_7 either. We need to not view hps' stack as= this : magical thing that solves all problems because we have at least RELEN= G_6 to : support for a while, and may have to support the current stack in REL= ENG_7 : too. : = : To be honest, I really wish Hans would be more pro-active in merging = changes : to the old stack so that the delta between it and his would be more : manageable. I've said this plenty of times privately, but no fixes t= o the : old stack have been forthcoming, not even new vendor IDs for existing= : drivers... : = : Warner : = : _______________________________________________ : freebsd-usb@freebsd.org mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-usb : To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org= " : = : = : = From owner-freebsd-usb@FreeBSD.ORG Mon May 28 20:23:06 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AFEFE16A400 for ; Mon, 28 May 2007 20:23:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 700DD13C480 for ; Mon, 28 May 2007 20:23:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4SKMTum019296; Mon, 28 May 2007 14:22:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 28 May 2007 14:22:46 -0600 (MDT) Message-Id: <20070528.142246.-169060603.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <465B2D8C.6050301@elischer.org> References: <000001c7a158$29592310$0202a8c0@artemis> <465B2D8C.6050301@elischer.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 28 May 2007 14:22:29 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: RE : UMASS pbm at startup 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: Mon, 28 May 2007 20:23:06 -0000 In message: <465B2D8C.6050301@elischer.org> Julian Elischer writes: : Alexandre DELAY wrote: : > But why does it work with an other motherboard and not with an other one? It : > is the same usb mass storage and the same system. Is it possible that it is : > due to IRQ interruptions? Maybe that the first motherboard doesn't have IRQ : > on USB port!? : > : : try a different USB port.. some motherboards do wierd things with some ports. That also suggests another workaround: Adding a 2.0 hub can paper over some problems too. Warner From owner-freebsd-usb@FreeBSD.ORG Mon May 28 20:26:34 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A014716A421 for ; Mon, 28 May 2007 20:26:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outT.internet-mail-service.net (outT.internet-mail-service.net [216.240.47.243]) by mx1.freebsd.org (Postfix) with ESMTP id 8BFF013C44C for ; Mon, 28 May 2007 20:26:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 28 May 2007 13:26:34 -0700 Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id AEA7A125A26; Mon, 28 May 2007 13:26:33 -0700 (PDT) Message-ID: <465B3B04.9090705@elischer.org> Date: Mon, 28 May 2007 13:26:44 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: Anish Mistry References: <200705281518.52086.amistry@am-productions.biz> In-Reply-To: <200705281518.52086.amistry@am-productions.biz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org Subject: Re: ETA on HPS USB stack into CURRENT? 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: Mon, 28 May 2007 20:26:34 -0000 Anish Mistry wrote: > What requirements still need to be met before the HPS USB stack is > committed to CURRENT? I understand that introducing a major > sub-system change so close the start of a release cycle can be very > disruptive. My main concern is that the RELENG_7 branch will be > arriving in the next couple months and imp@ mentioned in the (Re: > UMASS pbm at startup) thread that RELENG_7 might not see the new > stack. This means that we'll have to wait until an 8.x release > (2009?) until we see the new stack in a stock install. Also the > current stack will then need to be supported during the entire life > of RELENG_7 which will probably into at least late 2010. > From here on out the limitations of the current USB stack not being > MPSAFE will only become more apparent with more systems shipping with > multiple processors. Such as not allow CPUs to drop to C3 when USB > is loaded, performance issues, and various HID parsing problems. > With all that said what would be needed so that we could see the new > stack in 7.1 eventhough 7.0 would have the old stack? Though this > does seem to be asking for a lot of trouble since it would be a > STABLE branch. This is a question we've been discussing a lot. Your public question probably deserves a public answer. There are some requirements that all subsystems require. HPS's USB code is no different from others. I will borrow from a talk at BSDCan that talked about project dynamics.. 1/ "Bus factor" of the project must not increase. i.e. "number of developers that may be hit by a bus before the project is really screwed". (bigger is better) Currently the "bus factor of the existing USB code is about 5 (busy) people Bus factor of new code is 1 2/ The nuclear powerplant problem. The direct opposite from a "bikeshed". Everyone understands a bikeshed and they can all comment on it. Very few people understand a nuclear powerplant so sometimes they can get installed with almost no review and comment. When they go wrong however they go wrong in a big way and influence a lot. They tend to decrease the "bus factor" of a project. (not good). What this means: A large module needs comprehensive review by other developers. The module needs to be split up into chunks that can be reviewed by humans. Ether by implementing it as a sequence of patches to get from "Here" to "there" in understandable steps, or by heavily documenting it. Preferably with lots of diagrams etc. (see the papers in the "docs" section for some of the examples of what people have done in the past) The code needs to reviewed, which means that it needs to be well laid out and commented. I beieve HPS is currently going through his code commenting it. It's curently "under commented". He has also been asked to provide some sort of design document to assist the reviewers. To some extent this means that HPS must be willing to let the control of his code slip from his hads somewhat. None of this of course means that it will get in if the reviewers don't like what they see, but if they do it comes in when all issues are addressed. Unless a really superior competitor exists, which seems doubtful at this time. The biggest competitor th HPS's USB code is "fix the old USB code". he needs to demonstrate that his co de is superior to this option. BTW after "first cut reviews" (done with great pain on the undocumented code), current issues of concern (also somewhat present in the existing code) include Locking issues and interaction with the newbus/device framework. When the commented and documented version of the code become available then it wil be reviewed more thoroughly and more issues will be raised undoubtedly. Currently the lack of documentation has hindered review. Implementation details: New code modules such as this should be installed with a transition period. In other words, for a short while both new and old code should exist side-by-side in some way. This allows people who need teh functionality and cannot spare the time to debug the new code, to keep working while others can work on the new code. This has happenned severaltimes in the past, with #ifdefs etc. being used to compile a kernle with new or old versions of various modules (e.g. pcmcia code vs pccard/newcard, or fastforward vs. regular forwarding) HPS is hoping to be able to present his code to developers attending EuroBSDcon in some way, and has agreed to assist us in reviewing it by adding comments and other documentation. (in some cases adding back commenting that already existed but he removed from his versions of the files). Until now all the work on HPS's code has been on the technical side, and none of it has been on the project integration side of things. This often tends to be overlooked but if Hans-Peter can get that side of his act together He has a chance that it could be accepted well. (assuming that reviewing results in a well integrated result.) Anyhow this is the basic thrust of a long discussion that I and some other developers had at BSDCan.. Nothing very Surprising, but it does lay down a line which needs to be reached for integration of that code, and several of us have been communicationg these requirements to Hans-Peter. Finally, We REALLY do need good USB code, so we hope that when we can review it fully when it is documented, we discover that it is just wonderful, and that any issues that are raised by various domain experts (e.g. locking, interrupts, VM, device framework) are all addressed quickly and everyone gets what they need. Reality rarely lives up to that standard but that's what we hope :-) From owner-freebsd-usb@FreeBSD.ORG Mon May 28 20:28:46 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A71016A47F for ; Mon, 28 May 2007 20:28:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe12.swip.net [212.247.155.97]) by mx1.freebsd.org (Postfix) with ESMTP id AA59C13C4C7 for ; Mon, 28 May 2007 20:28:45 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [88.88.46.79] (account mc467741@c2i.net HELO [192.168.0.102]) by mailfe12.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 333166995; Mon, 28 May 2007 22:28:43 +0200 From: Hans Petter Selasky To: "M. Warner Losh" Date: Mon, 28 May 2007 22:28:32 +0200 User-Agent: KMail/1.9.5 References: <000001c7a148$94c5d9a0$0202a8c0@artemis> <200705281912.30389.hselasky@c2i.net> <20070528.120144.-957833410.imp@bsdimp.com> In-Reply-To: <20070528.120144.-957833410.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200705282228.33010.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: UMASS pbm at startup 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: Mon, 28 May 2007 20:28:46 -0000 On Monday 28 May 2007 20:01, M. Warner Losh wrote: > In message: <200705281912.30389.hselasky@c2i.net> > > Hans Petter Selasky writes: > : On Monday 28 May 2007 18:52, Aymeric MUNTZ (Cerbere3) wrote: > : > Hi, > : > > : > I have a pbm with my usb disk-key under freebsd. > : > When i start the system (FreeBSD 5.2) with the key already plugged, it > : > is not recognised. If I unplug and replug it, it is recognised. > : > With an other motherboard, I do not have this problem. > : > > : > Is there a way to rescan for usb devices? I already tried "camcontrol > : > rescan all" with no success. > : > : Have you tried the SVN version of the new USB stack with FreeBSD 6.2 > : installed? > > Let's just change one thing at a time... Try going to 6.2 first. > changing both the usb stack and the freebsd version at one time might > not be wise. We also need to track down problems in the current USB > stack, since we are never going to put hps' stack into RELENG_6. > Since it hasn't yet been committed to current and there's a freeze > coming up shortly, it is doubtful that it will be in RELENG_7 either. > We need to not view hps' stack as this magical thing that solves all > problems because we have at least RELENG_6 to support for a while, and > may have to support the current stack in RELENG_7 too. > > To be honest, I really wish Hans would be more pro-active in merging > changes to the old stack so that the delta between it and his would be > more manageable. I've said this plenty of times privately, but no > fixes to the old stack have been forthcoming, not even new vendor IDs > for existing drivers... My schedule is full. I'm tracking all changes going into HEAD at least. There are some deltas that could have been backported, but I do not specifically keep track of all the small things I fix. I would need a secretary for that :-) Any volunteers ;-) With regard to the topic of this thread I know about some specific issues that leaves the result that attached devices are not detected. This is related to missed PCD interrupts. You have to fake a PCD interrupt every time you enable the PCD again, to catch any missed PCD interrupts. The problem is the same with OHCI, but there this interrupt is called something else. The PCD interrupt is connected to the root interrupt endpoint on the root HUB, which is a virtual device. I think that this is the problem. --HPS From owner-freebsd-usb@FreeBSD.ORG Mon May 28 21:07:58 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2B3016A469 for ; Mon, 28 May 2007 21:07:58 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id AABB813C487 for ; Mon, 28 May 2007 21:07:58 +0000 (UTC) (envelope-from amistry@am-productions.biz) Received: from [192.168.1.100] (cpe-71-72-80-132.columbus.res.rr.com [71.72.80.132]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id l4SLbROd066554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 May 2007 17:37:35 -0400 (EDT) (envelope-from amistry@am-productions.biz) From: Anish Mistry Organization: AM Productions To: Julian Elischer Date: Mon, 28 May 2007 17:10:31 -0400 User-Agent: KMail/1.9.6 References: <200705281518.52086.amistry@am-productions.biz> <465B3B04.9090705@elischer.org> In-Reply-To: <465B3B04.9090705@elischer.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1646012.oDkXm7gv4E"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200705281710.41488.amistry@am-productions.biz> X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_50,MYFREEBSD3, RCVD_IN_NJABL_DUL,SPF_SOFTFAIL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.7/3311/Sun May 27 20:21:25 2007 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd-usb@freebsd.org Subject: Re: ETA on HPS USB stack into CURRENT? 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: Mon, 28 May 2007 21:07:59 -0000 --nextPart1646012.oDkXm7gv4E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 28 May 2007, Julian Elischer wrote: > Anish Mistry wrote: > > What requirements still need to be met before the HPS USB stack > > is committed to CURRENT? I understand that introducing a major > > sub-system change so close the start of a release cycle can be > > very disruptive. My main concern is that the RELENG_7 branch > > will be arriving in the next couple months and imp@ mentioned in > > the (Re: UMASS pbm at startup) thread that RELENG_7 might not see > > the new stack. This means that we'll have to wait until an 8.x > > release (2009?) until we see the new stack in a stock install.=20 > > Also the current stack will then need to be supported during the > > entire life of RELENG_7 which will probably into at least late > > 2010. From here on out the limitations of the current USB stack > > not being MPSAFE will only become more apparent with more systems > > shipping with multiple processors. Such as not allow CPUs to > > drop to C3 when USB is loaded, performance issues, and various > > HID parsing problems. With all that said what would be needed so > > that we could see the new stack in 7.1 eventhough 7.0 would have > > the old stack? Though this does seem to be asking for a lot of > > trouble since it would be a STABLE branch. > > This is a question we've been discussing a lot. Your public > question probably deserves a public answer. > > There are some requirements that all subsystems require. HPS's USB > code is no different from others. > > I will borrow from a talk at BSDCan that talked about project > dynamics.. > > 1/ "Bus factor" of the project must not increase. > i.e. "number of developers that may be hit by a bus before > the project is really screwed". (bigger is better) > > Currently the "bus factor of the existing USB code is about 5 > (busy) people Bus factor of new code is 1 > > 2/ The nuclear powerplant problem. > The direct opposite from a "bikeshed". > Everyone understands a bikeshed and they can all comment on it. > Very few people understand a nuclear powerplant so sometimes they > can get installed with almost no review and comment. When they go > wrong however they go wrong in a big way and influence a lot. > They tend to decrease the "bus factor" of a project. (not good). > > > What this means: > A large module needs comprehensive review by other developers. > The module needs to be split up into chunks that can be reviewed > by humans. Ether by implementing it as a sequence of patches to get > from "Here" to "there" in understandable steps, or by heavily > documenting it. Preferably with lots of diagrams etc. (see the > papers in the "docs" section for some of the examples of what > people have done in the past) > > The code needs to reviewed, which means that it needs to be well > laid out and commented. I beieve HPS is currently going through his > code commenting it. It's curently "under commented". He has also > been asked to provide some sort of design document to assist the > reviewers. To some extent this means that HPS must be willing to > let the control of his code slip from his hads somewhat. > > > None of this of course means that it will get in if the reviewers > don't like what they see, but if they do it comes in when all > issues are addressed. > > Unless a really superior competitor exists, which seems doubtful at > this time. The biggest competitor th HPS's USB code is "fix the old > USB code". he needs to demonstrate that his co de is superior to > this option. > > BTW after "first cut reviews" (done with great pain on the > undocumented code), current issues of concern (also somewhat > present in the existing code) include Locking issues and > interaction with the newbus/device framework. > > When the commented and documented version of the code become > available then it wil be reviewed more thoroughly and more issues > will be raised undoubtedly. Currently the lack of documentation has > hindered review. > > Implementation details: > > New code modules such as this should be installed with a transition > period. In other words, for a short while both new and old code > should exist side-by-side in some way. This allows people who need > teh functionality and cannot spare the time to debug the new code, > to keep working while others can work on the new code. This has > happenned severaltimes in the past, with #ifdefs etc. being used to > compile a kernle with new or old versions of various modules (e.g. > pcmcia code vs pccard/newcard, or fastforward vs. regular > forwarding) > > HPS is hoping to be able to present his code to developers > attending EuroBSDcon in some way, and has agreed to assist us in > reviewing it > by adding comments and other documentation. (in some cases adding > back commenting that already existed but he removed from his > versions of the files). > > > Until now all the work on HPS's code has been on the technical > side, and none of it has been on the project integration side of > things. This often tends to be overlooked but if Hans-Peter can get > that side of his act together He has a chance that it could be > accepted well. (assuming that reviewing results in a well > integrated result.) > > Anyhow this is the basic thrust of a long discussion that I and > some other developers had at BSDCan.. > > Nothing very Surprising, but it does lay down a line which needs to > be reached for integration of that code, and several of us have > been communicationg these requirements to Hans-Peter. > > Finally, We REALLY do need good USB code, so we hope that > when we can review it fully when it is documented, we discover that > it is just wonderful, and that any issues that are raised by > various domain experts (e.g. locking, interrupts, VM, device > framework) are all addressed quickly and everyone gets what they > need. > > Reality rarely lives up to that standard but that's what we hope > :-) Exactly the type of response that I was hoping for. Thanks for the=20 detailed explanation. =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart1646012.oDkXm7gv4E Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQBGW0VRxqA5ziudZT0RAi74AJ9usXpN2EQSWUNb9eOyD0vEmsH+nQCeN2Y2 cZCmHHK9fhQYIrT5YhjgRKk= =f/oP -----END PGP SIGNATURE----- --nextPart1646012.oDkXm7gv4E-- From owner-freebsd-usb@FreeBSD.ORG Tue May 29 01:00:16 2007 Return-Path: X-Original-To: freebsd-usb@hub.freebsd.org Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B850316A475 for ; Tue, 29 May 2007 01:00:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 8E50D13C4CA for ; Tue, 29 May 2007 01:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4T10ENB076680 for ; Tue, 29 May 2007 01:00:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4T10EqJ076676; Tue, 29 May 2007 01:00:14 GMT (envelope-from gnats) Date: Tue, 29 May 2007 01:00:14 GMT Message-Id: <200705290100.l4T10EqJ076676@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: Jonathan Fosburgh Cc: Subject: Re: kern/92083: [ural] [panic] panic using WPA on ural NIC in 6.2-RELEASE X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jonathan Fosburgh List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2007 01:00:16 -0000 The following reply was made to PR kern/92083; it has been noted by GNATS. From: Jonathan Fosburgh To: Anders Nordby Cc: bug-followup@freebsd.org, Sam Leffler Subject: Re: kern/92083: [ural] [panic] panic using WPA on ural NIC in 6.2-RELEASE Date: Mon, 28 May 2007 18:52:05 -0500 I'm being cautiously optimistic here. Late last week I switched over to the new USB stack amd started running my ural NIC with wpa_supplicant (still in WEP mode). So far, no new panics. I will run a few more days like this and then try switching my network to WPA. From owner-freebsd-usb@FreeBSD.ORG Wed May 30 04:44:07 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 005F816A468 for ; Wed, 30 May 2007 04:44:06 +0000 (UTC) (envelope-from andrew@dobrohot.org) Received: from smtp-6.masterhost.ru (smtp-6.masterhost.ru [83.222.24.106]) by mx1.freebsd.org (Postfix) with SMTP id 1317513C4B7 for ; Wed, 30 May 2007 04:44:05 +0000 (UTC) (envelope-from andrew@dobrohot.org) Received: (qmail 8794 invoked from network); 30 May 2007 04:43:48 -0000 Received: from one.globax.biz (HELO inspirra.localdomain) (izdat%dobrohot.org@81.177.8.165) by smtp1.masterhost.ru with SMTP; 30 May 2007 04:43:48 -0000 Received: from inspirra.localdomain (inspirra.localdomain [192.168.2.1]) by inspirra.localdomain (8.14.1/8.13.8) with ESMTP id l4U4gwdk002681 for ; Wed, 30 May 2007 08:42:58 +0400 (MSD) (envelope-from andrew@dobrohot.org) Message-ID: <465D00D1.2030705@dobrohot.org> Date: Wed, 30 May 2007 08:42:57 +0400 From: Andrew Muhametshin Organization: =?windows-1251?Q?=C0=CD=CE_=22=C4=EE=E1=F0=EE=F5=EE=F2=22?= User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Subject: umass0: Samsung VY-H350 Voice recorder 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: Wed, 30 May 2007 04:44:07 -0000 Hello It is not possible to connect the device "Samsung VY-H350 Voice recorder"... I installed the SVN version new USB a stack. =======START=========== May 30 07:53:16 inspirra kernel: umass0: May 30 07:53:16 inspirra kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 May 30 07:53:17 inspirra kernel: umass0:6:0:-1: Attached to scbus6 May 30 07:53:22 inspirra kernel: xptioctl: pass driver is not in the kernel May 30 07:53:22 inspirra kernel: xptioctl: put "device pass0" in your kernel config file May 30 07:53:27 inspirra kernel: (da0:umass-sim0:0:0:0): got CAM status 0x4 May 30 07:53:27 inspirra kernel: (da0:umass-sim0:0:0:0): fatal error, failed to attach to device May 30 07:53:27 inspirra kernel: (da0:umass-sim0:0:0:0): lost device May 30 07:53:27 inspirra kernel: (da0:umass-sim0:0:0:0): removing device entry $ ls /dev/pass0 /dev/pass0 $ uname -a FreeBSD inspirra.localdomain 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 30 03:46:39 MSD 2007 root@inspirra.localdomain:/SHARED/obj.inspirra/usr/src/sys/INSPIRRA i386 =======STOP============ Whether it as that to correct is possible? With the best regards Andrew M. From owner-freebsd-usb@FreeBSD.ORG Wed May 30 21:36:00 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 738D016A421 for ; Wed, 30 May 2007 21:36:00 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id D726613C44C for ; Wed, 30 May 2007 21:35:59 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so320473uge for ; Wed, 30 May 2007 14:35:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to; b=Ps8KKcAycRCzbQI74AF3k1zIR70GsD4iJklnYXQp6j0QM3Qa4gQ8sKRNkQV4o6AvAaPJdU8bvVFQzIyvcWbn+e0fJkY0ynnnI4PeGvHvCUa7I1tlUk2jbMzeGO2CzHva59PMMMs0YvncOrrsRntxwhIjl3v+S1f9/w+5fcXn9q8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to; b=qdKRVhVMtfXmiJXgDOyPEbgW3b/B4DJdeyjXum7e/NEX/k1R+kvO/ElUHYGci+LLdWkHShvifta4rgwDrGG9ZEDzdIiVxcn4gqG8/2HqP6ugDd4CVvVSV2kweueh0feRnkfYuKM3g+E2YHqFt6Eo6ZNNgnlaaHYxgnbtOo6QupM= Received: by 10.67.115.7 with SMTP id s7mr826625ugm.1180559336567; Wed, 30 May 2007 14:08:56 -0700 (PDT) Received: from roadrunner.q.local ( [85.180.140.72]) by mx.google.com with ESMTP id g1sm596764muf.2007.05.30.14.08.54; Wed, 30 May 2007 14:08:56 -0700 (PDT) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.14.1/8.14.1) with ESMTP id l4UL8gxL008573; Wed, 30 May 2007 23:08:42 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.q.local (8.14.1/8.14.1/Submit) id l4UL8gMx008572; Wed, 30 May 2007 23:08:42 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Wed, 30 May 2007 23:08:42 +0200 From: Ulrich Spoerlein To: Andrew Muhametshin Message-ID: <20070530210842.GD3592@roadrunner.q.local> Mail-Followup-To: Andrew Muhametshin , freebsd-usb@freebsd.org References: <465D00D1.2030705@dobrohot.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <465D00D1.2030705@dobrohot.org> Cc: freebsd-usb@freebsd.org Subject: Re: umass0: Samsung VY-H350 Voice recorder 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: Wed, 30 May 2007 21:36:00 -0000 Andrew Muhametshin wrote: > Hello > > It is not possible to connect the device "Samsung VY-H350 Voice recorder"... > I installed the SVN version new USB a stack. > > =======START=========== > May 30 07:53:16 inspirra kernel: umass0: addr 125> > May 30 07:53:16 inspirra kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 > May 30 07:53:17 inspirra kernel: umass0:6:0:-1: Attached to scbus6 > May 30 07:53:22 inspirra kernel: xptioctl: pass driver is not in the kernel > May 30 07:53:22 inspirra kernel: xptioctl: put "device pass0" in your kernel config file This might sound retarded, but could you please make sure, that da and pass are in your kernel. Best thing would be to check with: kldstat -v|egrep "da|pass" Ulrich Spoerlein -- "The trouble with the dictionary is you have to know how the word is spelled before you can look it up to see how it is spelled." -- Will Cuppy From owner-freebsd-usb@FreeBSD.ORG Thu May 31 01:01:36 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5E0516A400 for ; Thu, 31 May 2007 01:01:36 +0000 (UTC) (envelope-from andrew@dobrohot.org) Received: from smtp-4.masterhost.ru (smtp-4.masterhost.ru [83.222.24.104]) by mx1.freebsd.org (Postfix) with SMTP id DB7AF13C458 for ; Thu, 31 May 2007 01:01:35 +0000 (UTC) (envelope-from andrew@dobrohot.org) Received: (qmail 26131 invoked from network); 31 May 2007 01:01:18 -0000 Received: from one.globax.biz (HELO inspirra.localdomain) (izdat%dobrohot.org@81.177.8.165) by smtp1.masterhost.ru with SMTP; 31 May 2007 01:01:18 -0000 Received: from inspirra.localdomain (inspirra.localdomain [192.168.2.1]) by inspirra.localdomain (8.14.1/8.13.8) with ESMTP id l4V10jS3001507 for ; Thu, 31 May 2007 05:00:45 +0400 (MSD) (envelope-from andrew@dobrohot.org) Message-ID: <465E1E3D.1060203@dobrohot.org> Date: Thu, 31 May 2007 05:00:45 +0400 From: Andrew Muhametshin Organization: =?KOI8-R?Q?=E1=EE=EF_=22=E4=CF=C2=D2=CF=C8=CF=D4=22?= User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <465D00D1.2030705@dobrohot.org> <20070530210842.GD3592@roadrunner.q.local> In-Reply-To: <20070530210842.GD3592@roadrunner.q.local> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: umass0: Samsung VY-H350 Voice recorder 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: Thu, 31 May 2007 01:01:36 -0000 Ulrich Spoerlein wrote: > Andrew Muhametshin wrote: > >> Hello >> >> It is not possible to connect the device "Samsung VY-H350 Voice recorder"... >> I installed the SVN version new USB a stack. >> >> =======START=========== >> May 30 07:53:16 inspirra kernel: umass0: > addr 125> >> May 30 07:53:16 inspirra kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 >> May 30 07:53:17 inspirra kernel: umass0:6:0:-1: Attached to scbus6 >> May 30 07:53:22 inspirra kernel: xptioctl: pass driver is not in the kernel >> May 30 07:53:22 inspirra kernel: xptioctl: put "device pass0" in your kernel config file >> > > This might sound retarded, but could you please make sure, that da and > pass are in your kernel. Best thing would be to check with: > kldstat -v|egrep "da|pass" > Yes, these devices are in a kernel: $ kldstat -v|egrep "da|pass" 90 da 91 pass And they work, as I use "atapicam" for record of CD/DVD from k3b. Andrew R.Muhametshin From owner-freebsd-usb@FreeBSD.ORG Thu May 31 05:49:14 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D37E16A481 for ; Thu, 31 May 2007 05:49:14 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id 0CC8F13C46E for ; Thu, 31 May 2007 05:49:11 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 209.67.61.254 with SMTP; 31 May 2007 05:49:10 -0000 Date: Thu, 31 May 2007 08:48:45 +0300 From: Nikolay Pavlov To: imp@freebsd.org Message-ID: <20070531054845.GA22380@zone3000.net> References: <20070528093944.GA12606@zone3000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070528093944.GA12606@zone3000.net> X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-usb@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: ucom0: could not set data multiplex mode 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: Thu, 31 May 2007 05:49:14 -0000 On Monday, 28 May 2007 at 12:39:44 +0300, Nikolay Pavlov wrote: > Hi folks. > I have an issue with CCU-550 CDMA modem > (http://www.cmotech.com/eproduct6-1.htm) on recent current. > Every time i am reattaching it i see this error: > ucom0: could not set data multiplex mode > > So in order to work with it i have to reboot after each detache > procedure. The only known workaround for this is to delete the > "goto bad;" code in /usr/src/sys/dev/usb/umodem.c: > > printf("%s: could not set data multiplex mode\n", > devname); > goto bad; > > Could someone comment on this? > > P.S. Please cc me, becuase i am not subscribe to freebsd-usb or > freebsd-mobile > May be i should send this to maintainer..? -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-usb@FreeBSD.ORG Thu May 31 07:04:54 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EDB2316A46D; Thu, 31 May 2007 07:04:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 918ED13C457; Thu, 31 May 2007 07:04:54 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4V74J6s059191; Thu, 31 May 2007 01:04:19 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 31 May 2007 01:04:36 -0600 (MDT) Message-Id: <20070531.010436.-460543608.imp@bsdimp.com> To: quetzal@zone3000.net From: "M. Warner Losh" In-Reply-To: <20070531054845.GA22380@zone3000.net> References: <20070528093944.GA12606@zone3000.net> <20070531054845.GA22380@zone3000.net> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 31 May 2007 01:04:19 -0600 (MDT) Cc: freebsd-usb@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: ucom0: could not set data multiplex mode 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: Thu, 31 May 2007 07:04:55 -0000 In message: <20070531054845.GA22380@zone3000.net> Nikolay Pavlov writes: : On Monday, 28 May 2007 at 12:39:44 +0300, Nikolay Pavlov wrote: : > Hi folks. : > I have an issue with CCU-550 CDMA modem : > (http://www.cmotech.com/eproduct6-1.htm) on recent current. : > Every time i am reattaching it i see this error: : > ucom0: could not set data multiplex mode : > : > So in order to work with it i have to reboot after each detache : > procedure. The only known workaround for this is to delete the : > "goto bad;" code in /usr/src/sys/dev/usb/umodem.c: : > : > printf("%s: could not set data multiplex mode\n", : > devname); : > goto bad; : > : > Could someone comment on this? : > : > P.S. Please cc me, becuase i am not subscribe to freebsd-usb or : > freebsd-mobile : > : : May be i should send this to maintainer..? I thought that NetBSD did something clever in this condition, but it doesn't. Try adding the device to usb_quirks.c. You'll need an entry like the following: { USB_VENDOR_METRICOM, USB_PRODUCT_METRICOM_RICOCHET_GS, 0x100, { UQ_ASSUME_CM_OVER_DATA }}, for whatever values your CCU-550 CDMA modem has. alternatively, you could try the following patch, which may be lame: Index: umodem.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v retrieving revision 1.60 diff -u -r1.60 umodem.c --- umodem.c 7 Sep 2006 00:06:42 -0000 1.60 +++ umodem.c 31 May 2007 07:03:49 -0000 @@ -279,7 +279,6 @@ usb_cdc_cm_descriptor_t *cmd; char *devinfo = NULL; const char *devname; - usbd_status err; int data_ifcno; int i; struct ucom_softc *ucom; @@ -373,16 +372,8 @@ } else { if (sc->sc_cm_cap & USB_CDC_CM_OVER_DATA) { if (sc->sc_acm_cap & USB_CDC_ACM_HAS_FEATURE) - err = umodem_set_comm_feature(sc, - UCDC_ABSTRACT_STATE, UCDC_DATA_MULTIPLEXED); - else - err = 0; - if (err) { - printf("%s: could not set data multiplex mode\n", - devname); - goto bad; - } - sc->sc_cm_over_data = 1; + umodem_set_comm_feature(sc, + UCDC_ABSTRACT_STATE, UCDC_DATA_MULTIPLEXED); sc->sc_cm_over_data = 1; } } this patch just feels wrong to me, but I suspect it will just work. Warner From owner-freebsd-usb@FreeBSD.ORG Thu May 31 21:28:27 2007 Return-Path: X-Original-To: usb@freebsd.org Delivered-To: freebsd-usb@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15CA316A421; Thu, 31 May 2007 21:28:27 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.freebsd.org (Postfix) with ESMTP id E658A13C457; Thu, 31 May 2007 21:28:26 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn03.u.washington.edu (hymn03.u.washington.edu [140.142.12.169]) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l4VLSQ05005978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 May 2007 14:28:26 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn03.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4VLSQbr021751; Thu, 31 May 2007 14:28:26 -0700 X-Auth-Received: from [192.55.52.4] by hymn03.u.washington.edu via HTTP; Thu, 31 May 2007 14:28:25 PDT Date: Thu, 31 May 2007 14:28:26 -0700 (PDT) From: youshi10@u.washington.edu To: hackers@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.5.31.140735 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SUPERLONG_LINE 0.05, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: usb@freebsd.org, stable@freebsd.org, doc@freebsd.org, current@freebsd.org Subject: Re: Kernel panicking in 6.2 and 7-CURRENT -- interrupt issues 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: Thu, 31 May 2007 21:28:27 -0000 On Tue, 29 May 2007 youshi10@u.washington.edu wrote: > Hello, > I'm trying to install 7-CURRENT on my desktop, locally instead of on a > virtual machine, and I'm running into an issue where the kernel almost always > panics on boot with my motherboard (ASUS P5N-SLI E), due to some sort of > interrupt assignment / probing issues. > > Observations: > 1. 7-CURRENT (built) never properly detects the interrupts on the system. > 2. 7-CURRENT (May ISO snapshot) doesn't properly detect my USB keyboard, > but boots and runs sysinstall. > 3. 6.2 RELEASE panics if I don't boot FreeBSD up into "safe mode", due to > an issue with the ohci driver (I think the error message had something to deal > with device adding / enumeration and not being able to find a memory / > interrupt address). > > First off, if I could get some of the command line arguments to pass to > the kernel to emulate safe-mode, that would be much appreciated. Second off, if > anybody has any ideas on how to debug this issue, I'll go off and try to > determine what the cause is. If it's anything like it was before (clean out > /usr/obj, rebuild), I'll be ok. Otherwise, I'll have to purchase more parts and > build another dedicated FreeBSD system :(.. > > Thanks, > -Garrett Sorry for cross-posting so much, but this information is relevant to all of the mailing lists included. Ok I "solved" my problem, to a certain extent. Basically the ASUS P5N-E SLI motherboard (nVidia chipset) isn't bootable with FreeBSD 6.2 RELEASE without going into SAFE MODE (panics after ohci_add_done looking for a non-existent memory address, if the USB controller is enabled in the BIOS with "Legacy Mode", i.e. USB Keyboard compatible), and isn't compatible with FreeBSD 7 at all (kernel can't map IRQs properly on up-to-date CURRENT and panics in kernel mode during boot). Strangely enough the 7-CURRENT snapshot ISOs work, but then again it doesn't setup the OHCI and USB keyboard stuff properly, and I can't get any sort of input from my keyboard, obviously. The ASUS P5B-DLX motherboard (Intel chipset) is compatible with FreeBSD 6.2 and 7 though, without any hacks. Maybe someone should update some documentation on the release notes page for supported hardware? Thanks, -Garrett PS Please CC me in any communication as I'm not subscribed to doc@, stable@, or usb@. From owner-freebsd-usb@FreeBSD.ORG Sat Jun 2 11:25:48 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 380A416A46B for ; Sat, 2 Jun 2007 11:25:48 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp813.mail.ird.yahoo.com (smtp813.mail.ird.yahoo.com [217.146.188.73]) by mx1.freebsd.org (Postfix) with SMTP id 8557113C489 for ; Sat, 2 Jun 2007 11:25:47 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 85772 invoked from network); 2 Jun 2007 10:59:05 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=BZ7vW2zL0O3rFQG1DSs2UuYp5r20oEc5Op4r3QVO/u4eNjJKhRFLUz+Cq5n6CcWhQQOzyKrymuiYakBFxKdQg2p5yAVB00yc3zC9ppJBvVU2GbtdG1Wz1D+6AY/4C4Jkm3RbvXVG0ClX7tNR369JSJ+dwm2ak4jNlO+M6nKL80A= ; Received: from unknown (HELO ?192.168.0.22?) (thomas.sparrevohn@btinternet.com@86.143.69.86 with login) by smtp813.mail.ird.yahoo.com with SMTP; 2 Jun 2007 10:59:04 -0000 X-YMail-OSG: _K4RmVIVM1kchuoO3LzgjqTIYBhn94CUaJdk1sE2f37_jIU1UBxO90ujJWC73QA1mcWuYTiZYxxtoECGwlwwIQXWUndhsPEBrJhTl13_bn_fKxq1hwsvGWSAgeQ- From: Thomas Sparrevohn To: freebsd-usb@freebsd.org Date: Sat, 2 Jun 2007 11:59:04 +0100 User-Agent: KMail/1.9.6 References: <200705281518.52086.amistry@am-productions.biz> <20070528.141729.-1962670642.imp@bsdimp.com> In-Reply-To: <20070528.141729.-1962670642.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706021159.04378.Thomas.Sparrevohn@btinternet.com> Subject: Re: ETA on HPS USB stack into CURRENT? 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: Sat, 02 Jun 2007 11:25:48 -0000 On Monday 28 May 2007 21:17:29 M. Warner Losh wrote: > In message: <200705281518.52086.amistry@am-productions.biz> > Anish Mistry writes: > : What requirements still need to be met before the HPS USB stack is > : committed to CURRENT? > > It will go into the into the tree when it is ready. The FreeBSD > project has a policy that all significant code must be reviewed before > it goes into the tree, and that the concerns that have been raised in > the review be addressed. This process is ongoing with the hps usb > stack, and when it is complete, it will go into current. > > Warner > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > Great From owner-freebsd-usb@FreeBSD.ORG Sat Jun 2 12:24:53 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0802416A41F for ; Sat, 2 Jun 2007 12:24:53 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id C0EC413C480 for ; Sat, 2 Jun 2007 12:24:52 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 0 with SMTP; 2 Jun 2007 12:24:51 -0000 Date: Sat, 2 Jun 2007 15:24:53 +0300 From: Nikolay Pavlov To: "M. Warner Losh" Message-ID: <20070602122453.GA48237@zone3000.net> References: <20070528093944.GA12606@zone3000.net> <20070531054845.GA22380@zone3000.net> <20070531.010436.-460543608.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070531.010436.-460543608.imp@bsdimp.com> X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-usb@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: ucom0: could not set data multiplex mode 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: Sat, 02 Jun 2007 12:24:53 -0000 On Thursday, 31 May 2007 at 1:04:36 -0600, M. Warner Losh wrote: > In message: <20070531054845.GA22380@zone3000.net> > Nikolay Pavlov writes: > : On Monday, 28 May 2007 at 12:39:44 +0300, Nikolay Pavlov wrote: > : > Hi folks. > : > I have an issue with CCU-550 CDMA modem > : > (http://www.cmotech.com/eproduct6-1.htm) on recent current. > : > Every time i am reattaching it i see this error: > : > ucom0: could not set data multiplex mode > : > > : > So in order to work with it i have to reboot after each detache > : > procedure. The only known workaround for this is to delete the > : > "goto bad;" code in /usr/src/sys/dev/usb/umodem.c: > : > > : > printf("%s: could not set data multiplex mode\n", > : > devname); > : > goto bad; > : > > : > Could someone comment on this? > : > > : > P.S. Please cc me, becuase i am not subscribe to freebsd-usb or > : > freebsd-mobile > : > > : > : May be i should send this to maintainer..? > > I thought that NetBSD did something clever in this condition, but it > doesn't. Try adding the device to usb_quirks.c. You'll need an entry > like the following: > > { USB_VENDOR_METRICOM, USB_PRODUCT_METRICOM_RICOCHET_GS, > 0x100, { UQ_ASSUME_CM_OVER_DATA }}, Thanks for response Warner. I want to check the usb_quirks variant first. Could you please advise me on what this line should be if i have this on dmesg: ucom0: on uhub1 ucom0: CMOTECH CO., LTD. CMOTECH CDMA Technologies, rev 2.00/0.00, addr 2, iclass 2/2 ucom0: data interface 1, has CM over data, has break ucom0: status change notification available > > for whatever values your CCU-550 CDMA modem has. alternatively, you > could try the following patch, which may be lame: > > Index: umodem.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v > retrieving revision 1.60 > diff -u -r1.60 umodem.c > --- umodem.c 7 Sep 2006 00:06:42 -0000 1.60 > +++ umodem.c 31 May 2007 07:03:49 -0000 > @@ -279,7 +279,6 @@ > usb_cdc_cm_descriptor_t *cmd; > char *devinfo = NULL; > const char *devname; > - usbd_status err; > int data_ifcno; > int i; > struct ucom_softc *ucom; > @@ -373,16 +372,8 @@ > } else { > if (sc->sc_cm_cap & USB_CDC_CM_OVER_DATA) { > if (sc->sc_acm_cap & USB_CDC_ACM_HAS_FEATURE) > - err = umodem_set_comm_feature(sc, > - UCDC_ABSTRACT_STATE, UCDC_DATA_MULTIPLEXED); > - else > - err = 0; > - if (err) { > - printf("%s: could not set data multiplex mode\n", > - devname); > - goto bad; > - } > - sc->sc_cm_over_data = 1; > + umodem_set_comm_feature(sc, > + UCDC_ABSTRACT_STATE, UCDC_DATA_MULTIPLEXED); sc->sc_cm_over_data = 1; > } > } > > > this patch just feels wrong to me, but I suspect it will just work. > > > Warner -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-usb@FreeBSD.ORG Sat Jun 2 19:11:30 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BB3B116A468; Sat, 2 Jun 2007 19:11:30 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6BD4F13C44B; Sat, 2 Jun 2007 19:11:30 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l52J9puN000920; Sat, 2 Jun 2007 13:09:52 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 02 Jun 2007 13:10:11 -0600 (MDT) Message-Id: <20070602.131011.-1370572280.imp@bsdimp.com> To: quetzal@zone3000.net From: "M. Warner Losh" In-Reply-To: <20070602122453.GA48237@zone3000.net> References: <20070531054845.GA22380@zone3000.net> <20070531.010436.-460543608.imp@bsdimp.com> <20070602122453.GA48237@zone3000.net> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 02 Jun 2007 13:09:52 -0600 (MDT) Cc: freebsd-usb@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: ucom0: could not set data multiplex mode 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: Sat, 02 Jun 2007 19:11:30 -0000 In message: <20070602122453.GA48237@zone3000.net> Nikolay Pavlov writes: : On Thursday, 31 May 2007 at 1:04:36 -0600, M. Warner Losh wrote: : > In message: <20070531054845.GA22380@zone3000.net> : > Nikolay Pavlov writes: : > : On Monday, 28 May 2007 at 12:39:44 +0300, Nikolay Pavlov wrote: : > : > Hi folks. : > : > I have an issue with CCU-550 CDMA modem : > : > (http://www.cmotech.com/eproduct6-1.htm) on recent current. : > : > Every time i am reattaching it i see this error: : > : > ucom0: could not set data multiplex mode : > : > : > : > So in order to work with it i have to reboot after each detache : > : > procedure. The only known workaround for this is to delete the : > : > "goto bad;" code in /usr/src/sys/dev/usb/umodem.c: : > : > : > : > printf("%s: could not set data multiplex mode\n", : > : > devname); : > : > goto bad; : > : > : > : > Could someone comment on this? : > : > : > : > P.S. Please cc me, becuase i am not subscribe to freebsd-usb or : > : > freebsd-mobile : > : > : > : : > : May be i should send this to maintainer..? : > : > I thought that NetBSD did something clever in this condition, but it : > doesn't. Try adding the device to usb_quirks.c. You'll need an entry : > like the following: : > : > { USB_VENDOR_METRICOM, USB_PRODUCT_METRICOM_RICOCHET_GS, : > 0x100, { UQ_ASSUME_CM_OVER_DATA }}, : : Thanks for response Warner. I want to check the usb_quirks variant : first. Could you please advise me on what this line should be if i have : this on dmesg: : : ucom0: on uhub1 : ucom0: CMOTECH CO., LTD. CMOTECH CDMA Technologies, rev 2.00/0.00, addr 2, iclass 2/2 : ucom0: data interface 1, has CM over data, has break : ucom0: status change notification available Unfortunately, there's not enough info there. usbdevs -v will tell us. : > for whatever values your CCU-550 CDMA modem has. alternatively, you : > could try the following patch, which may be lame: : > : > Index: umodem.c : > =================================================================== : > RCS file: /home/ncvs/src/sys/dev/usb/umodem.c,v : > retrieving revision 1.60 : > diff -u -r1.60 umodem.c : > --- umodem.c 7 Sep 2006 00:06:42 -0000 1.60 : > +++ umodem.c 31 May 2007 07:03:49 -0000 : > @@ -279,7 +279,6 @@ : > usb_cdc_cm_descriptor_t *cmd; : > char *devinfo = NULL; : > const char *devname; : > - usbd_status err; : > int data_ifcno; : > int i; : > struct ucom_softc *ucom; : > @@ -373,16 +372,8 @@ : > } else { : > if (sc->sc_cm_cap & USB_CDC_CM_OVER_DATA) { : > if (sc->sc_acm_cap & USB_CDC_ACM_HAS_FEATURE) : > - err = umodem_set_comm_feature(sc, : > - UCDC_ABSTRACT_STATE, UCDC_DATA_MULTIPLEXED); : > - else : > - err = 0; : > - if (err) { : > - printf("%s: could not set data multiplex mode\n", : > - devname); : > - goto bad; : > - } : > - sc->sc_cm_over_data = 1; : > + umodem_set_comm_feature(sc, : > + UCDC_ABSTRACT_STATE, UCDC_DATA_MULTIPLEXED); sc->sc_cm_over_data = 1; : > } : > } : > : > : > this patch just feels wrong to me, but I suspect it will just work. Please try this patch too :-) Warner