> 1) A loadable driver is an *.o file right?? > Are there any special flags that need to be used to > compile? I think that in your mind you mix various concepts. An .o file is an object file. It may be a kernel driver or something like else. Do you want to code a kernel driver or a PC/SC driver (also called IFDHandler) for your reader? If you want to do an IFDHandler you may used the developer kit from [1]. An IFDHandler is a library loaded by PC/SC Lite.
> 2) I have a *.o file but when I try to use modprobe to > load the module it gives me an error saying it can't > locate the module here is what i type: > # /sbin/modprobe /home/froilan/mydriver.o > have also tried the same except "mydriver" Here you can try to load your driver as a kernel driver but I am not sure that a kernel driver are authorized to use an external high level API such as libusb because I imagine your driver is based on a such API. It seems to me that "modprobe" without option take a module name and not a path with the name. See the modprobe's manpage or else type "insmod /home/froilan/mydriver.o" > 3) My device which i'm trying to write a driver is > very simple all I need to do is be able to send > commands to it and receive commands from it? Is there > a way to avoid having to write a driver and maybe use > an existing one. To write a PC/SC driver (IFDHandler) for an USB reader you can based your code on the generic CCID driver [2]. But if you have not the specifications it may be hard. You may also change your reader :-). Which is your reader? [1] http://linuxnet.com/drivers/readers/files/ifd-devkit-1.0.0.tar.gz [2] http://pcsclite.alioth.debian.org/ccid.html Regards, Damien Sauveron ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
