From owner-freebsd-current Sat Apr 15 13:51:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C504237B57A for ; Sat, 15 Apr 2000 13:51:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA44297; Sat, 15 Apr 2000 14:51:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA10875; Sat, 15 Apr 2000 14:50:37 -0600 (MDT) Message-Id: <200004152050.OAA10875@harmony.village.org> To: John Hay Subject: Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles Cc: acid@cn.ua (Michael Vasilenko), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 15 Apr 2000 10:30:17 +0200." <200004150830.KAA95900@zibbi.mikom.csir.co.za> References: <200004150830.KAA95900@zibbi.mikom.csir.co.za> Date: Sat, 15 Apr 2000 14:50:37 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004150830.KAA95900@zibbi.mikom.csir.co.za> John Hay writes: : our problem is even before a (non) working interrupt would come into the : picture. I'd have to say that based on the evidence so far, that the interrupts aren't getting routined correctly, or that there's an interrupt conflict. This is almost certainly at the cardbus bridge layer, even though I don't want it to be :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message