- From: Jan Gukelberger <g.u.g.i_at_gmx.de>
- Date: Tue, 01 Mar 2005 01:13:21 +0100
On Sun, 2005-02-27 at 14:48 -0500, Kenneth Jacker wrote: > >> Should I be 'insmod'ing 'kcomedilib.ko'? > > jg> Yes. :-) > > Thanks, Jan, I eventually figured that out! > > What is in *your* list of installed modules under RTAI? jan_at_elessar:~$ lsmod|egrep '(come|rtai)' kcomedilib 13696 0 rtai_fifos 38796 0 comedi_fc 3008 1 cb_pcidas64 comedi 40960 4 kcomedilib,cb_pcidas64,comedi_fc,8255 rtai_lxrt 75448 3 kcomedilib,rtai_fifos,cb_pcidas64 rtai_hal 28948 5 kcomedilib,rtai_fifos,cb_pcidas64,comedi,rtai_lxrt > How do you "get things going" under RTAI? atm I have a simple script modprobe'ing all necessary modules and issuing a comedi_config. Something like this: modprobe rtai_hal modprobe rtai_fifos modprobe cb_pcidas64 modprobe comedi_rt_timer modprobe kcomedilib comedi_config /dev/comedi0 cb_pcidas64 For "real" use I plan to figure out the necessary modprobe.conf lines for doing this automatically at device open time but it's still a long way until we can use our application for "real" lab work as this is a rather large setup with data acquisition only being one component. So I haven't looked at this yet. > I'm having other, new problems as well ... :-( > > What is the first argument to comedi_open()? An integer? A string? A string specifying the device path just as the user space version. You may find it useful to consult the kcomedilib include file linux/include/comedilib.h in conjunction with the Comedi handbook. HTH, Jan
Received on 2005-03-01Z00:13:21