From owner-freebsd-current@FreeBSD.ORG Mon Oct 17 03:03:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 7E27B16A41F for ; Mon, 17 Oct 2005 03:03:43 +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 F352B43D48 for ; Mon, 17 Oct 2005 03:03:42 +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 j9H31fKo024177; Sun, 16 Oct 2005 21:01:41 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 16 Oct 2005 21:02:55 -0600 (MDT) Message-Id: <20051016.210255.65497697.imp@bsdimp.com> To: emaste@phaedrus.sandvine.ca From: "M. Warner Losh" In-Reply-To: <20051016202721.GA10256@sandvine.com> References: <20051016202721.GA10256@sandvine.com> 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]); Sun, 16 Oct 2005 21:01:42 -0600 (MDT) Cc: freebsd-current@freebsd.org Subject: Re: DWL-650 (RTL8180L) cardbus issue (Expecting link target, got 0xcc) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 03:03:43 -0000 In message: <20051016202721.GA10256@sandvine.com> Ed Maste writes: : Is there a way to forcibly power up the slot, so that I can e.g. poke : around with pciconf? I'm not very familiar with cardbus support. It : appears that pccardc is supposed to be able to turn the slot on but : relies on a nonexistent /dev/card0. /dev/card0 is OLDCARD. There's no way to power things back up, short of hacking pccbb.c. But even that wouldn't help you, since I don't think pciconf -l works on cardbus cards very well.... However, it won't help you. Your problem is resource allocation. When we allocate the memory to read the CIS, something conflicts so we can't map the CIS there. that's why you are seeing odd things. I'd try setting hw.cbb.start_memory=0x5200000 and other addresses that aren't 0x88000000. Warner