Date: Thu, 28 Nov 2002 23:57:57 +0100 (CET) From: Dirk-Willem van Gulik <dirkx@webweaving.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-hackers@FreeBSD.ORG, <wleiden@xs4all.nl> Subject: Re: Understanding PCI intr routing on a Cirrus Logic PD6729 Message-ID: <20021128235301.I25692-100000@foem.leiden.webweaving.org> In-Reply-To: <20021128.104629.127817773.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28 Nov 2002, M. Warner Losh wrote: > this is bogus. However, a less bogus version is: > > /* > * Tell the chip to do its routing thing. > */ > sc->chip->func_intr_way(&sc->slots[0], sc->func_route); > sc->chip->csc_intr_way(&sc->slots[0], sc->csc_route); > > The reason that cardbus_init is bogus in this context is that it > messes with pci config registers that aren't present on the 6729. Ack :-) > Can you try that out? Hmm - no cookie; worse than before. With the cardbus init -all was essentially functional as far as I could test; but in with the above the timeouts have returned - abeit in a differnt form; rather than a simple Timeout I see: wi1: timeout in wi_cmd 0x0002; event status 0x8000 wi1: timeout in wi_cmd 0x0000; event status 0x8000 wi1: wi_cmd: busy bit won't clear. wi1: wi_cmd: busy bit won't clear. wi1: init failed wi1: wi_cmd: busy bit won't clear. wi1: wi_cmd: busy bit won't clear. .... wi1: wi_cmd: busy bit won't clear. wi1: wi_cmd: busy bit won't clear. wi1: wi_cmd: busy bit won't clear. wi1: wi_cmd: busy bit won't clear. So something in the cardbus_init() may be needed ? Dw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021128235301.I25692-100000>