From owner-freebsd-hackers  Fri Sep 13 06:36:34 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA19881
          for hackers-outgoing; Fri, 13 Sep 1996 06:36:34 -0700 (PDT)
Received: from relay.philips.nl (ns.philips.nl [130.144.65.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA19873
          for <freebsd-hackers@freebsd.org>; Fri, 13 Sep 1996 06:36:29 -0700 (PDT)
Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id PAA24899; Fri, 13 Sep 1996 15:35:03 +0200
Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP
	id sma023289; Fri Sep 13 15:25:05 1996
Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id PAA11831; Fri, 13 Sep 1996 15:27:54 +0200
Received: (from guido@localhost) 
	by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id PAA17480; Fri, 13 Sep 1996 15:24:57 +0200
From: Guido van Rooij <Guido.vanRooij@nl.cis.philips.com>
Message-Id: <199609131324.PAA17480@spooky.lss.cp.philips.com>
Subject: Re: vx device broken in 21.1.5?
To: dfr@render.com (Doug Rabson)
Date: Fri, 13 Sep 1996 15:24:57 +0200 (MET DST)
Cc: freebsd-hackers@freebsd.org
Reply-To: Guido.vanRooij@nl.cis.philips.com
In-Reply-To: <Pine.BSF.3.95.960913123758.4396V-100000@minnow.render.com> from Doug Rabson at "Sep 13, 96 12:40:09 pm"
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Doug Rabson wrote:
> 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.
> 

I don't beleive it is the hardware. Lot's of FreeBSD ppl see this while the
author of the driver for NetBSD doesn't know this behaviour.

Indeed I patched it that way. Though unfortunately it will give less
perfomance.

-Guido