[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libusb and usbdevfs
[snip]
> >> Without a driver i may not be able to communicate to the device like
> >> normal read write etc. But shouldnt it be visible to me through sysfs
> >> interface?
> >
> >Yes it should.
> Yes it is now visible. But problem is now it recognizes it as webcam
> :(. Though it is not. How big is this problem?
What is it really? Why would the kernel be confused this way?
Greg the device is a USB I/O card. I dont know why is kernel confused
this way? But it loads the USB serial webcam driver for it , dont know
why.
I moved the webcam driver from the build and still it detects it but
now it doesnt loads any module for it, why? And still manages to
detect it ... :(
> or is it a problem at all? On the other hand can question specially to
> Greg :). You rewrote ezusb.c in the source tree for 2.6.x kernel. I
> want to use it but i somehow cant. Can i somehow use cypress_m8 module
> instead of ezusb module?
Please provide specifics as to why you can not use the ezusb.c calls in
your driver. It works for me.
I havent written the driver yet, so didnt try the ezusb calls:).
The board contains Anchor chip's EZ USB FX2 chip( now cypress chip).
> I tried but cypress_m8 module doesnot identifies the card at all :(.
I don't understand, why would different random drivers work with this
device. What type of device is it? What is the output of
/proc/bus/usb/devices with the device plugged in?
there is no such thing devices in my /proc/bus/usb/ :(.
does it mean i ll have to write a driver for it ? And may be then use
ezusb's methods?
TIA
thanks,
greg k-h
--
play the game
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/