From owner-freebsd-mobile Thu Mar 7 14:20:23 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 70FD037B402; Thu, 7 Mar 2002 14:20:16 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g27MKEi95046; Thu, 7 Mar 2002 15:20:14 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g27MKCL97380; Thu, 7 Mar 2002 15:20:12 -0700 (MST) (envelope-from imp@village.org) Date: Thu, 07 Mar 2002 15:20:03 -0700 (MST) Message-Id: <20020307.152003.123976395.imp@village.org> To: jhb@FreeBSD.org Cc: mobile@FreeBSD.org Subject: Re: NEWCARD doesn't like my cardbus card anymore From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message: John Baldwin writes: : Warner, : : Looks like recent newcard still doesn't like my cardbus dc0. Adding the : IO_RANGE option didn't help. It looks like the CIS that newcard finds for the : card doesn't have any BAR's for memory or IO, so bus_alloc_resource() freaks : out when the dc driver tries to allocate resources for those BARs. When it : panics (I know you've fixed hte panic, but I think the card would still not : probe now): : : cardbus0: Expecting link target, got 0x59 : cardbus0: Resource not specified in CIS: id=10, size=100 : cardbus0: Resource not specified in CIS: id=14, size=400 : pccbb alloc res fail : : When it works on an old kernel: : : found-> vendor=0x13d1, dev=0xab02, revid=0x11 : class=02-00-00, hdrtype=0x00, mfdev=0 : cmdreg=0x0000, statreg=0x0290, cachelnsz=8 (dwords) : lattimer=0xa8 (5040 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) : intpin=a, irq=128 : cardbus0: Expecting link target, got 0x59 : cardbus0: Resource not specified in CIS: id=10, size=100 : cardbus0: Resource not specified in CIS: id=14, size=400 : cardbus0: Non-prefetchable memory at 84002000-840023ff : cardbus0: Non-prefetchable memory rid=14 at 84002000-840023ff (400) : cardbus0: IO port at 1100-11ff : cardbus0: IO port rid=10 at 1100-11ff : dc0: port 0x1100-0x11ff mem 0x84002000-0x840023ff i : rq 11 at device 0.0 on cardbus0 : : Note that the PCI-ish dump doesn't include any BAR's for 0x10 and 0x14. Is : there a bug in our CIS reading code maybe? Or perhaps this is a bum card? I don't think that you have PCI_ALLOW_UNSUPPORTED_IO_RANGE defined, or you'd get some spewage. The 0x84000000 address is the old fallback address, and the pci bridge is now filtering that out. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message