From owner-freebsd-current Mon Feb 8 16:21:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01231 for freebsd-current-outgoing; Mon, 8 Feb 1999 16:21:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01222 for ; Mon, 8 Feb 1999 16:21:42 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.2/8.9.1) id QAA63814; Mon, 8 Feb 1999 16:22:05 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199902090022.QAA63814@troutmask.apl.washington.edu> Subject: Re: gpib driver - does anybody use it? In-Reply-To: <863e4g4gqk.fsf@niobe.ewox.org> from Dag-Erling Smorgrav at "Feb 9, 1999 0:29: 7 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Mon, 8 Feb 1999 16:22:05 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > I stumbled upon the (undocumented) gpib driver today - apparently for > the "National Instruments AT-GPIB and AT-GPIB/TNT board", according to > LINT. Apart from staticization sweeps, -Wall fixes and the like, > nobody's touched it since 1995. Does anybody have an AT-GPIB board, or > even know what it is? Does the driver actually work? Is there a good > reason (or any reason at all) why we shouldn't just bobbit it? > Actually, John Galbraith has written a better driver for the National Instrument GPIB cards. Search the hardware mailing list for a URL to his latest driver. It is reported to be superior to the driver in src/sys. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message