Date: Fri, 14 Apr 2000 13:52:25 -0600 From: Warner Losh <imp@village.org> To: Michael Vasilenko <acid@cn.ua> Cc: John Hay <jhay@mikom.csir.co.za>, freebsd-current@FreeBSD.ORG Subject: Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles Message-ID: <200004141952.NAA58759@harmony.village.org> In-Reply-To: Your message of "Fri, 14 Apr 2000 20:41:54 %2B0300." <Pine.BSF.4.21.0004142030520.34509-100000@wicket.ci.net.ua> References: <Pine.BSF.4.21.0004142030520.34509-100000@wicket.ci.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.21.0004142030520.34509-100000@wicket.ci.net.ua> Michael Vasilenko writes: : : : On Fri, 14 Apr 2000, John Hay wrote: : : > Delete or rename /dev/card1 and you should get further. It will most : > probably still not work, but it won't hang anymore. : : Thanks, it still don't work, but didn't hang anymore :) : : > 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? : : The situation is interesting - when I remove /dev/card1,2,3, pccardd : get started, ifconfig wi0 works, but on any xmit - ping, etc.. : I've got: : : wi0: xmit failed : wi0: tx buffer allocation failed : wi0: device timeout : : and pccardd didn't catch pccard events - removing and inserting cards... You have interrupt problems. Don't share with anything else. Don't use interrupts of *ANY* other hardware in your system *AT*ALL*. I'll be the first to talk about how bad interrupt choice is in the current pccard code. I'm also one of the first to be doing something about it with NEWCARD... :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004141952.NAA58759>