1) Comedi lock locks the subdevice so that other processes/modules can't do much with it except query it. It helps ensure that the state of the subdevice doesn't change.
2) Ok, there are actually two slightly different comedi api's. One is the user-space api, which is probably the one you were reading. The other is the kernel api. The kernel api strongly resembles the user-space one except that things like comedi_open return ints, etc. Look in the kernel version of comedilib.h (it might be in the comedi source tree under include/linux). Since this is a kernel module, one has no choice but to use kcomedilib. I hope this answers your questions! :) -Calin On Tue, 30 Oct 2001, Massimiliano Cialdi wrote: > "Calin A. Culianu" wrote: > > > > I use rtlinux 3.1 comedi 0.7.60 and a national instruments pci-6024e > > > board. > > > where can I find some docs and examples? > > Hi! I am using comedi with an NI AT-MIO 16E board... I am working on > > custom software for data acquisition. Our current version, which is > > I downloaded DAQ System software. > In the file rt_process.c there are some unclear things in module_init() > function: > 1- why you use functions like comedi_lock() before opening the device > (comedi_open())? How can it works? > 2- in comedilib reference the description for comedi_open is: > http://stm.lbl.gov/comedi/doc/comedilib-6.html#ss6.2 > it returns comedi_t* but you assign it to an int; you pass 0 istead of > device name as parameter. How can it works? > > thanks and sorry for my english. > -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
