From owner-freebsd-mobile Wed Apr 1 09:06:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06275 for freebsd-mobile-outgoing; Wed, 1 Apr 1998 09:06:41 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06252 for ; Wed, 1 Apr 1998 09:06:38 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA14940; Wed, 1 Apr 1998 10:06:33 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA15632; Wed, 1 Apr 1998 10:06:30 -0700 Date: Wed, 1 Apr 1998 10:06:30 -0700 Message-Id: <199804011706.KAA15632@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthias.Apitz@SOFTCON.de (Matthias Apitz) Cc: nate@mt.sri.com (Nate Williams), freebsd-mobile@FreeBSD.ORG Subject: Re: 3c589D and pccard support in FreeBSD 2.2.5 In-Reply-To: <9804011900.AA01719@kant.SOFTCON.de> References: <199803311614.JAA11050@mt.sri.com> <9804011900.AA01719@kant.SOFTCON.de> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It's probably not a mis-configured IRQ then. > > Not sure -- see below. .... > ... For every pkg > the routine if->watchdog gets called for a missing interupt. So, the interrupt routine isn't getting called. This is definitely a sign. Can you see if the interrupt routine is called at all? > So the problem isn't in user-land (e.g. routing or ARP or DNS), > it's in kernel-land. Is there someone who is "in charge" for > that driver code or someone who can offer the internal programmers > manual for that card (3C589D)? Thx. I don't have one, but I can tell with certain assurance that the driver/software works on dozens of laptops, if not hundreds right now. I'd like into the interrupt generation code in the PCIC controller. I'm about 99.9% sure it's not and issue with if_ep.c, but probably in /sys/pccard. Somehow your controller is not getting correctly programmed to generate interrupts for the card, hence the reason you're not getting them. (This is assuming you're using the PCCARD code.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message