From owner-freebsd-hackers Fri Sep 13 04:46:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA14977 for hackers-outgoing; Fri, 13 Sep 1996 04:46:35 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA14970 for ; Fri, 13 Sep 1996 04:46:28 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id MAA08787; Fri, 13 Sep 1996 12:40:09 +0100 Date: Fri, 13 Sep 1996 12:40:09 +0100 (BST) From: Doug Rabson To: Guido van Rooij cc: freebsd-hackers@freebsd.org Subject: Re: vx device broken in 21.1.5? In-Reply-To: <199609130900.LAA03640@spooky.lss.cp.philips.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 13 Sep 1996, Guido van Rooij wrote: > I just ported the current Open/NetBSD if_vx driver to FreeBSD 2.1.5 and > I am seeeing the exact same problems. > > I've ben assured that these drivers do work. > > What happens in FreeBSD is when vxstart() is called and there is not > enough space free in the fifos, a treshold is set so the board will > give an interrupt when the amount of free space in the fifos pass > the treshold. > > Unfortunately, there is *never* one single interrupts given for this event. > It just doesn't happen. Therefor OACTIVE stays set. > > Accoring to me, everything is done by the book (read: the OpenBSD driver): > RD_0_MASK and INTR_MASK both contain TX_AVAIL at the > interrupt time so TX_AVAIL should be set. I also printed the actuial free > space in the interrupts handler. It started lower then the treshold and > ended higher but there was *no* interrupt given where the status had the > TX_AVAIL flag set. > > Any hints? No idea. Sounds like busted hardware to me. You could always try to patch it up with some kind of timeout instead of waiting for TX_AVAIL. Surely the card should at least deliver a transmit-complete interrupt for the packet which was in the fifo. Maybe you could use that to restart transmission. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426