Date: Thu, 07 Mar 2002 18:10:35 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: "M. Warner Losh" <imp@village.org> Cc: mobile@FreeBSD.org Subject: Re: NEWCARD doesn't like my cardbus card anymore Message-ID: <XFMail.020307181035.jhb@FreeBSD.org> In-Reply-To: <20020307.152003.123976395.imp@village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07-Mar-02 M. Warner Losh wrote: > In message: <XFMail.020307171507.jhb@FreeBSD.org> > John Baldwin <jhb@FreeBSD.org> 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: <Abocom FE2500 10/100BaseTX> 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. [17:27:29] (ttypa) john@laptop:/sys/i386/conf > grep ALLOW LAPTOP options PCI_ALLOW_UNSUPPORTED_IO_RANGE That's the option, right? [17:28:41] (ttypa) john@laptop:...i386/compile/LAPTOP > cat opt_pci.h #define PCI_ALLOW_UNSUPPORTED_IO_RANGE 1 :-/ > Warner -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.020307181035.jhb>