From owner-freebsd-current@FreeBSD.ORG Wed Jun 11 16:08:46 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88F0237B401 for ; Wed, 11 Jun 2003 16:08:45 -0700 (PDT) Received: from ion.gank.org (ion.gank.org [198.78.66.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDE5B43FD7 for ; Wed, 11 Jun 2003 16:08:44 -0700 (PDT) (envelope-from craig@xfoil.gank.org) Received: from localhost (ion.gank.org [198.78.66.164]) by ion.gank.org (GankMail) with ESMTP id 8B4802CFA9; Wed, 11 Jun 2003 18:08:44 -0500 (CDT) Received: from ion.gank.org ([198.78.66.164]) by localhost (ion.gank.org [198.78.66.164]) (amavisd-new, port 10024) with LMTP id 48267-03; Wed, 11 Jun 2003 18:08:44 -0500 (CDT) Received: from [172.22.8.188] (pix.corelab.com [12.45.169.2]) by ion.gank.org (GankMail) with ESMTP id D711A2BB50; Wed, 11 Jun 2003 18:08:43 -0500 (CDT) From: Craig Boston To: ticso@cicely.de In-Reply-To: <20030611193734.GO26807@cicely12.cicely.de> References: <1055260269.91337.127.camel@owen1492.uf.corelab.com> <20030611193734.GO26807@cicely12.cicely.de> Content-Type: text/plain Message-Id: <1055372921.24204.50.camel@owen1492.uf.corelab.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.92 (Preview Release) Date: 11 Jun 2003 23:08:42 +0000 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: CardBus USB 2.0 Controller (NEC uPD) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 23:08:46 -0000 On Wed, 2003-06-11 at 19:37, Bernd Walter wrote: > There are known problems with USB2.0 cardbus cards. > We have some kind of resource problem - Warner already wrote something > about it some time ago. Ah, thanks. Any hints on where to find it? I tried adding his name to my archive/google searches but keep coming up with many unrelated posts... :-/ About all I've managed to do so far is to verify that it doesn't appear to be an interrupt routing problem. The driver is indeed receiving interrupts. However the status register only says that it's a root hub status change, never to advise that a transfer is complete :-( Polling mode doesn't seem to help as it queries the same register... It also sometimes interrupts with intrs==0 right after a transfer starts, which sounds bogus to me. I'm in single-user mode and positive that nothing else on irq 11 is interrupting. Oh well, for now I'm content to just keep hacking on it and learn more about how the code works :) Craig