- From: David Schleef <ds_at_schleef.org>
- Date: Mon, 25 Aug 2003 13:58:40 -0700
On Fri, Aug 22, 2003 at 09:23:13AM +0200, Christoph Hinterm?ller wrote: > > These are both discussed in the section about configuration > > instructions and extended triggering in the Comedilib manual. > > > When reading the INSN_CONFIG section I'm a bit confused. > What the hell are these ids and where to put them. > Are they a more detailed INSN_CONFIG flag for insn field in insn struct ? > And why than the IDs for digital io configuration are named COMEDI_INPUT > COMEDI_OUTPUT COMEDI_OPENDRAIN and not > INSN_CONFIG_COMEDI_INPUT INSN_CONFIG_COMEDI_OUTPUT and > INSN_CONFIG_COMEDI_OPENDRAIN. You want me to name things consistently? How silly! :) > Or are they sent to driver via data field of insn_config structure. Indeed. insn->data[0] determines what type of configuration it is. insn->n and the other data array elements depend on the type of configuration. COMEDI_INPUT and COMEDI_OUTPUT just happen to use insn->n == 1. They don't need extra configuration, since they also make use of insn->chanspec. dave...
Received on 2003-08-25Z19:58:40