On Wed, Sep 21, 2011 at 06:59:57PM +0530, Felix Varghese wrote:
Does anybody have anything to add or oppose on this or would you guys
rather have me send a patch along with my changes?
Patches are always best, we can review that and go from there.
greg k-h
On Mon, Sep 19, 2011 at 11:13:33AM +0530, Felix Varghese wrote:
Just do:
modprobe usb_serial vendor=0x product=0x
with the proper vendor and product ids for your device, then plug it in.
No kernel changes needed at all, just have a pair of bulk in/out
endpoints and all
You might be right and the code might be wrong, care to send a patch for
it correcting the issue?
Would be glad to do that, if I am able to resolve the issue.
Meanwhile, any insights from anybody on this would be welcome!
Regards,
Felix.
___
Just do:
modprobe usb_serial vendor=0x product=0x
with the proper vendor and product ids for your device, then plug it in.
No kernel changes needed at all, just have a pair of bulk in/out
endpoints and all will work automatically for you.
Thanks Greg, I had thought that the
On Thu, Sep 15, 2011 at 07:02:59PM +0530, Felix Varghese wrote:
Hi,
I have been trying to communicate with a custom usb device from a
SAM9G20-EK board using the usb-skeleton.c driver example in the linux
source. I modified the driver to add my device's vendor and product
id. The USB device
Hi,
I have been trying to communicate with a custom usb device from a
SAM9G20-EK board using the usb-skeleton.c driver example in the linux
source. I modified the driver to add my device's vendor and product
id. The USB device enumerates with two bulk endpoints - one IN and one
OUT. The
