- From: Luc Lefebvre <luc.lefebvre_at_mcgill.ca>
- Date: Fri, 14 Nov 2003 15:25:43 -0500
Hi Dave, Thanks for the quick response. I edited my kernel .config to CONFIG_PCMCIA=m and and compiled the comedi modules. It proceeded to compile the ni_mio_cs module (and others). I then rebooted the computer with the NIDAQ-6062E and it was recognized (using pcmcia-cs v3.2.5, not the kernel pcmcia support). I then did comedi_calibrate /dev/comedi0 and it did everything OK except that it complained about not being able to create the calibration file (somewhere/libcomedi0/calibrations/...., the default location). I then did: comedi_calibrate -S /root/comedi/calibrations/ni_mio_cs_DAQCard-6062E_comedi0 And that worked fine. If there is anything else that I can do, please let me know. cheers On Fri, 14 Nov 2003 12:13:45 -0800 David Schleef <ds_at_schleef.org> wrote: > On Fri, Nov 14, 2003 at 02:16:07PM -0500, Luc Lefebvre wrote: > > Hi, > > > > I am using pcmcia-cs v3.2.5 (on Debian) with kernel 2.4.22 (not > > the kernel pcmcia drivers, both pcmcia-cs and in kernel pcmcia > > have issues with my laptop). The problem is that whenever I do > > make-kpkg the configure script runs (I can't seem to manually > > configure the thing) and reads from my kernel .config. I could > > edit the .config and run this again, but there must be a better way. > > Does it work correctly if you force CONFIG_PCMCIA=y or m? That is, > if you compile Comedi against PCMCIA in the kernel, does it just > work with the external PCMCIA packages? If so, it would be wise > to add a --force-pcmcia option to ./configure. I don't think this > is a good idea in general, though. > > Otherwise, it would be wise to add support for compiling against > external PCMCIA sources. > > > > dave... > -- Luc Lefebvre In the beginner's mind there are many possibilities, in the expert's mind there are few. <Shunryu Suzuki> Key fingerprint = D2E5 5E35 B910 6F4E 0242 EC63 0FD9 96D0 C7F4 784E
Received on 2003-11-14Z20:25:43