- From: Christoph Hintermüller <christoph.hintermueller_at_umit.at>
- Date: Tue, 26 Aug 2003 07:44:19 +0200
Hi Am Montag, 25. August 2003 22:58 schrieb David Schleef: > You want me to name things consistently? How silly! :) No I just was confused by the id thing and the statement for extended triggering. > > > 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. Do i get that right when setting insn->flag to INSN_CONFIG. - The first element in insn->data allways has to be one of the id's like COMEDI_OUTPUT or what ever is assigned to different configuration sections stated in manual or 0 if not assigned or necessary. - If an id requires more complex configuration and/or settings these appear in insn->data fields with index >= 1. As it would be for ext_trigg configuration and some otheres. Ok this is logic although i wouldn't have got that when simply reading the comedi manual. - So when now extending ni-pcidio driver am i allowed to assign primary id's to extended triggering to meet my needs or would it be better to have some driver specific local id's in insn->data[>=1] or simply let id still not assigned? - Is there any recommended naming scheme for comedi. From reading manual it seems so but are there any rules i should obey when selecting names for config ids, parameter labels ... ?? cu Christoph -- Dipl.-Ing. Christoph Hintermüller University for Health Informatics and Technology Tyrol Innrain 98, A-6020 Innsbruck, AUSTRIA Tel: +43/ 512/ 58 67 34/ 820; Fax: +43/ 512/ 58 67 34/ 850 Mail: christoph.hintermueller_at_umit.at; Hompage: http://imsb.umit.at
Received on 2003-08-26Z04:44:19