Re: [fprint] Adding new driver

2012-01-30 Thread Patrick Marlier
On 01/30/2012 01:18 PM, MOGANESHWARAN RAJASEGARAN wrote: I tested the driver with libfprint-0.4.0. And too bad it cannot work. Why? Any specific reason? libusb problem? If you give more information, I hope some people can help you. -- Patrick. ___ fp

Re: [fprint] Adding new driver

2012-01-30 Thread MOGANESHWARAN RAJASEGARAN
I tested the driver with libfprint-0.4.0. And too bad it cannot work. On Thu, Jan 26, 2012 at 5:08 AM, MOGANESHWARAN RAJASEGARAN < mogan...@fkegraduate.utm.my> wrote: > Hi, > > It should be libusb.h. I was working on libfprint-0.0.6 and got it working > there. And I changed it to libfprint-0.4.0

Re: [fprint] Adding new driver

2012-01-25 Thread MOGANESHWARAN RAJASEGARAN
Hi, It should be libusb.h. I was working on libfprint-0.0.6 and got it working there. And I changed it to libfprint-0.4.0 by just replacing the usb_bulk_write and usb_bulk_read to libusb_bulk_transfer. I did remove some redundant parts in the driver source file. As for the following part which ha

Re: [fprint] Adding new driver

2012-01-25 Thread Patrick Marlier
On 01/24/2012 01:31 PM, MOGANESHWARAN RAJASEGARAN wrote: Thank you for the guide in creating the unified diff. I hope this is correct. The diff seems ok (weird http://?) and thanks for sharing your work and contributing. Main general concerns from my point of view (even if I am not either th

Re: [fprint] Adding new driver

2012-01-24 Thread Patrick Marlier
On 01/24/2012 10:55 AM, MOGANESHWARAN RAJASEGARAN wrote: Hi, I am having trouble creating the diff file for the newly written source file for eikontouch 300. I named it upeket.c. The source code is based on upektc.c. So how to create the diff file if there is no other source file to diff it? Or s

Re: [fprint] Adding new driver

2012-01-24 Thread MOGANESHWARAN RAJASEGARAN
Hi, I am having trouble creating the diff file for the newly written source file for eikontouch 300. I named it upeket.c. The source code is based on upektc.c. So how to create the diff file if there is no other source file to diff it? Or should I use upektc.c to create the diff file. And how about

Re: [fprint] Adding new driver

2012-01-23 Thread Bastien Nocera
On Sat, 2012-01-21 at 00:14 +0800, MOGANESHWARAN RAJASEGARAN wrote: > Sorry. > Have never done submitting a patch or report a bug. And did not know > about http://bugzilla.freedesktop.org. So I do not know the procedure > of submitting the source code. > Thanks for the guide. Create a unified d

Re: [fprint] Adding new driver

2012-01-20 Thread MOGANESHWARAN RAJASEGARAN
Sorry. Have never done submitting a patch or report a bug. And did not know about http://bugzilla.freedesktop.org. So I do not know the procedure of submitting the source code. Thanks for the guide. Regards, Moganesh On Fri, Jan 20, 2012 at 11:29 PM, Bastien Nocera wrote: > On Thu, 2012-01-19

Re: [fprint] Adding new driver

2012-01-20 Thread Bastien Nocera
On Thu, 2012-01-19 at 20:52 +0800, MOGANESHWARAN RAJASEGARAN wrote: > I have successfully make the UPEK EikonTouch 300 work with libfprint. > So how can I send the source code for the particular fingerprint > scanner? No need to send your message again, we received it fine the first time. In fact

Re: [fprint] Adding new driver

2012-01-19 Thread MOGANESHWARAN RAJASEGARAN
I have successfully make the UPEK EikonTouch 300 work with libfprint. So how can I send the source code for the particular fingerprint scanner? On Tue, Jan 17, 2012 at 2:36 PM, MOGANESHWARAN RAJASEGARAN < mogan...@fkegraduate.utm.my> wrote: > I have managed to get the driver starting. Now I have

Re: [fprint] Adding new driver

2012-01-16 Thread MOGANESHWARAN RAJASEGARAN
I have managed to get the driver starting. Now I have to add the protocol. On Tue, Jan 17, 2012 at 1:56 AM, Andrej Kruták wrote: > you can search for all occurances of the string "vfs101" and do it the > same way for your new driver... > > On Mon, Jan 16, 2012 at 5:14 PM, MOGANESHWARAN RAJASEG

Re: [fprint] Adding new driver

2012-01-16 Thread Andrej Kruták
you can search for all occurances of the string "vfs101" and do it the same way for your new driver... On Mon, Jan 16, 2012 at 5:14 PM, MOGANESHWARAN RAJASEGARAN < mogan...@fkegraduate.utm.my> wrote: > I have modified the files for libfprint-0.4.0. After that what should i > do? I ./configure and

Re: [fprint] Adding new driver

2012-01-16 Thread MOGANESHWARAN RAJASEGARAN
I have modified the files for libfprint-0.4.0. After that what should i do? I ./configure and make but in the makefile does not have the upek eikon touch (upeket). On Mon, Jan 16, 2012 at 11:16 PM, Bastien Nocera wrote: > On Mon, 2012-01-16 at 23:05 +0800, MOGANESHWARAN RAJASEGARAN wrote: > > I

Re: [fprint] Adding new driver

2012-01-16 Thread Bastien Nocera
On Mon, 2012-01-16 at 23:05 +0800, MOGANESHWARAN RAJASEGARAN wrote: > I was using libfprint-0.0.6. So I could not find all_drivers, for > loop, enable_xxx list and AM_CONDITIONAL list. But I did chnahe to > libfprint-0.1.0. But the new driver named upeket is not created in > makefile. Did I miss an

Re: [fprint] Adding new driver

2012-01-16 Thread MOGANESHWARAN RAJASEGARAN
I was using libfprint-0.0.6. So I could not find all_drivers, for loop, enable_xxx list and AM_CONDITIONAL list. But I did chnahe to libfprint-0.1.0. But the new driver named upeket is not created in makefile. Did I miss any procedure? Regards, Moganesh On Mon, Jan 16, 2012 at 4:21 PM, MOGANESHWA

Re: [fprint] Adding new driver

2012-01-16 Thread Bastien Nocera
On Mon, 2012-01-16 at 16:21 +0800, MOGANESHWARAN RAJASEGARAN wrote: > Hi, > > I have Upek EikonTouch 300. I create the driver based on upek > touchchip (upektc.c). I am having trouble compiling the newly created > driver for upek eikontouch300 (upeket.c). I dont know how to add this > source file

[fprint] Adding new driver

2012-01-16 Thread MOGANESHWARAN RAJASEGARAN
Hi, I have Upek EikonTouch 300. I create the driver based on upek touchchip (upektc.c). I am having trouble compiling the newly created driver for upek eikontouch300 (upeket.c). I dont know how to add this source file to the makefile. Regards, Moganesh