kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Cannot read using USB Skeleton Driver
Date: Mon, 19 Sep 2011 05:38:45 -0700	[thread overview]
Message-ID: <20110919123845.GA8951@kroah.com> (raw)
In-Reply-To: <CAKRE6muE9yrWxN91xFd1d1g4+0qPh3uvEy9cVNr2QMH-Pm2EvA@mail.gmail.com>

On Mon, Sep 19, 2011 at 11:13:33AM +0530, Felix Varghese wrote:
> > Just do:
> > ? ? ? ?modprobe usb_serial vendor=0x0000 product=0x0000
> > 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 usbserial driver would only work
> with proper CDC class virtual COM devices.
> I compiled it and tried it on my device and it worked fine! I was able
> to do bidirectional communication. So at least now I can be sure that
> one end is working. But the same device with the same firmware still
> doesn't work with the (customized) usb-skeleton. What could be wrong?

As I don't know what you customized exactly, nor how your hardware
exactly works, I could not say, sorry.

greg k-h

  reply	other threads:[~2011-09-19 12:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 13:32 Cannot read using USB Skeleton Driver Felix Varghese
2011-09-16  7:01 ` Greg KH
2011-09-16 11:29   ` Felix Varghese
2011-09-16 14:31     ` Greg KH
2011-09-19  5:43       ` Felix Varghese
2011-09-19 12:38         ` Greg KH [this message]
2011-09-19 13:21           ` Felix Varghese
2011-09-19 13:46             ` Greg KH
2011-09-20  3:49               ` Felix Varghese
2011-09-21 13:29                 ` Felix Varghese
2011-09-21 16:00                   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110919123845.GA8951@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).