From owner-freebsd-usb@FreeBSD.ORG Wed Jan 25 17:39:33 2006 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5208016A41F for ; Wed, 25 Jan 2006 17:39:33 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E3343D77 for ; Wed, 25 Jan 2006 17:39:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0PHaZC7035653; Wed, 25 Jan 2006 10:36:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 25 Jan 2006 10:36:35 -0700 (MST) Message-Id: <20060125.103635.71123032.imp@bsdimp.com> To: hselasky@c2i.net From: Warner Losh In-Reply-To: <200601251409.22020.hselasky@c2i.net> References: <43D4B4A9.40908@gmx.de> <200601251409.22020.hselasky@c2i.net> X-Mailer: Mew version 3.3 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]); Wed, 25 Jan 2006 10:36:36 -0700 (MST) Cc: LoN_Kamikaze@gmx.de, freebsd-usb@freebsd.org Subject: Re: PCMCIA USB card problems 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, 25 Jan 2006 17:39:33 -0000 > On Monday 23 January 2006 11:49, [LoN]Kamikaze wrote: > > I've got an 4 Port PCMCIA connector with a VIA chipset. > > The manual claims it's an OHCI/EHCI device, but FreeBSD identifies it as > > an VIA 83C572 UHCI device. After the identification there is a > > nonesaying errormessage and the system crashs. > > > > Compiling the kernel without UHCI I get the following output when I put > > the card into the slot: > > > > cardbus0: Expecting link target, got 0xff > > cardbus0: Resource not specified in CIS: id=14, size=100 > > cardbus0: Resource not specified in CIS: id=20, size=20 > > cardbus0: at device 0.0 (no driver attached) > > cardbus0: Expecting link target, got 0xff > > cardbus0: Resource not specified in CIS: id=14, size=100 > > cardbus0: Resource not specified in CIS: id=20, size=20 > > cardbus0: at device 0.1 (no driver attached) > > cardbus0: Expecting link target, got 0xff > > cardbus0: Resource not specified in CIS: id=10, size=100 > > cardbus0: Resource not specified in CIS: id=14, size=100 > > ehci1: mem > > 0xc0208000-0xc02080ff,0xc0209000-0xc02090ff irq 11 at device 0.2 on > > cardbus0 ehci1: [GIANT-LOCKED] > > usb1: EHCI version 1.0 > > usb1: wrong number of companions (2 != 0) > > ^^ this check should just be dropped from the code > > You can lookup the code in "/sys/dev/usb/ehci.c" and make it not return an > error when the number of companions mismatch. since I had exactly this error before my changes to the resource allocation stuff, but not after, I don't think that such a change would make things work. There's a number of diffrent bacnks of resources for these cards, and due to the resource allocation issues, they are getting cross threaded. Warner