From owner-freebsd-questions  Wed Sep 18 07:41:50 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA22538
          for questions-outgoing; Wed, 18 Sep 1996 07:41:50 -0700 (PDT)
Received: from sci.brooklyn.cuny.edu (eastham.sci.brooklyn.cuny.edu [146.245.1.21])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA22490
          for <questions@freebsd.org>; Wed, 18 Sep 1996 07:41:41 -0700 (PDT)
Received: from robeson.sci.brooklyn.cuny.edu by sci.brooklyn.cuny.edu (4.1/SMI-4.1a)
	id AA03599; Wed, 18 Sep 96 10:38:59 EDT
Received: by robeson.sci.brooklyn.cuny.edu (SMI-8.6/SMI-SVR4)
	id KAA22006; Wed, 18 Sep 1996 10:37:17 -0400
Date: Wed, 18 Sep 1996 10:37:17 -0400
Message-Id: <199609181437.KAA22006@robeson.sci.brooklyn.cuny.edu>
From: Dayton Clark <dayton@sci.brooklyn.cuny.edu>
To: hdalog@zipnet.net
Cc: questions@freebsd.org, pencil@holiday.sci.brooklyn.cuny.edu
In-Reply-To: <199609181016.GAA24326@hda.com> (message from Peter Dufault on
	Wed, 18 Sep 1996 06:16:10 -0400 (EDT))
Subject: Re: LabPC+ problem
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Thanks Peter.

<.> > 
<.> > We're using the labpc driver with FreeBSD 2.1R.  The system is a
<.> > straight forward 486/33 with ISA bus.  The board is a LabPC+.
...
<.> 
<.> I assume you defeated the multiple open lockout to permit you
<.> to open the digital and analog channels?  That should be OK.
<.> 
<.> The board and driver should support scanning - I'm using
<.> it in an application at a clients to scan in five channels.  Check
<.> the minor number to make sure you are scanning from the correct
<.> device - it has a field to set the upper bound on the scanning
<.> sequence.  Then use "dd" to read from that device and see if you
<.> are getting all channels, eliminating problems with your user
<.> code and pointing the finger at the driver.
<.> Finally, see if there is a boundary issue with eight channels.

Great suggestions.

<.> 
<.> > If we are to venture further into the driver, do you have any words of
<.> > wisdom on as to how to overcome the problem?  A specific question is:
<.> > why is the multi-open lockout necessary?
<.> 
<.> The multi open lockout is to prevent you from trying to open the device
<.> in, for example, scanning mode where it will scan through a channel
<.> list and also in fixed-channel mode where you read a single channel.
<.> 
<.> The driver would have to be made a lot smarter than it is to handle
...

As I suspected.

Thanks again.

dayton