From owner-freebsd-current Fri Apr 14 12:51: 8 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 9633E37B54C for ; Fri, 14 Apr 2000 12:51:05 -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 NAA38276; Fri, 14 Apr 2000 13:51:01 -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 NAA58732; Fri, 14 Apr 2000 13:50:41 -0600 (MDT) Message-Id: <200004141950.NAA58732@harmony.village.org> To: John Hay Subject: Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles Cc: acid@cn.ua (Michael I. Vasilenko), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 14 Apr 2000 18:57:38 +0200." <200004141657.SAA74896@zibbi.mikom.csir.co.za> References: <200004141657.SAA74896@zibbi.mikom.csir.co.za> Date: Fri, 14 Apr 2000 13:50:41 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004141657.SAA74896@zibbi.mikom.csir.co.za> John Hay writes: : You probably also have to tell pccardd to use the same interrupt that : pcic-pci0 got, because I don't see how else it can work, but I'm not : sure. I mean a PCI card can't generate different interrupts than the : one(s) connected to its pins can it? No. You have to tell pcic to use that interrupt. and tell pccardd to *NOT* use that interrupt. Interrupt sharing rarely works when pccard is in the mix. Don't do it, unless you know what you are doing. And even then, if anything at all doesn't work, stop doing it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message