From owner-freebsd-current  Sat Mar 28 22:26:07 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA08291
          for freebsd-current-outgoing; Sat, 28 Mar 1998 22:26:07 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08286
          for <current@FreeBSD.ORG>; Sat, 28 Mar 1998 22:26:04 -0800 (PST)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA01177;
	Sat, 28 Mar 1998 22:24:04 -0800 (PST)
Message-Id: <199803290624.WAA01177@implode.root.com>
To: Nathan Dorfman <nathan@rtfm.net>
cc: current@FreeBSD.ORG
Subject: Re: VX driver in current acting up? 
In-reply-to: Your message of "Sat, 28 Mar 1998 16:52:04 EST."
             <19980328165204.62437@rtfm.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 28 Mar 1998 22:24:04 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>    I'm more inclined to believe that the driver is broken, but it could be
>> either.
>
>Is it ever going to be fixed? Is there not enough demand? I would fix
>it if someone would throw me a clue as to how :-)

   Someone mentioned recently that they were working on a rewrite that will
use the advanced (e.g. DMA) features, so perhaps the new version will fix
the problems of the current driver.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message