From owner-freebsd-bugs Wed May 17 07:42:28 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA05294 for bugs-outgoing; Wed, 17 May 1995 07:42:28 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA05288 for ; Wed, 17 May 1995 07:42:26 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA21806; Wed, 17 May 1995 10:42:16 -0400 Date: Wed, 17 May 1995 10:42:16 -0400 From: Garrett Wollman Message-Id: <9505171442.AA21806@halloran-eldar.lcs.mit.edu> To: Noses Cc: freebsd-bugs@freefall.cdrom.com Subject: kern/428: ethernet cards and their drivers In-Reply-To: <199505170430.VAA19438@freefall.cdrom.com> References: <199505170427.GAA00955@oink.rhein.de> <199505170430.VAA19438@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < said: > device ep0 at isa? port 0x360 net irq 15 vector edintr <---- > Instead of not working, pinging a neighbour on the ethernet is giving you > decreasing times starting at 1000 ms going down 10 ms per packet. It drove > me slightly nuts until I found that typo - I replaced the board twice and > even used our LAN analyzer... Couldn't you add a big boot kicking me next > time I do it or get it not to work at all? One of the changes which will be required for LKM device drivers is to move the registration of interrupt handlers into the device's attach routine, which will eliminate this problem completely. I would have done this before but have had no time. If nobody else gets to it before I reorganize devconf the next time, I'll look into doing it then. Please, somebody get to it before then! -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant