From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: satish kumar <satish_shak@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How vendor specific drivers communicate
Date: Fri, 10 Aug 2001 08:47:34 -0700 [thread overview]
Message-ID: <3B740216.FD13A444@osdlab.org> (raw)
In-Reply-To: <20010810050402.24532.qmail@web20302.mail.yahoo.com>
satish kumar wrote:
>
> Hi,
>
> Please tell me , where can i get the complete
> scenerio of, how the vendor specific driver (composite
> device )communicate with USB drivers present in Linux.
Hi-
I think that you would get better answers by asking
your questions on linux-usb-devel@lists.sourceforge.net .
See http://www.linux-usb.org for some information, such as
the Linux-USB User's Guide and the Linux-USB Programming Guide.
For anything more than that, you'll probably need to ask
more specific questions.
In general, USB devices are handled at their interface
level, so if a USB device presents multiple USB
"interfaces," then a separate driver can communicate
to each interface.
--
~Randy
prev parent reply other threads:[~2001-08-10 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 5:04 How vendor specific drivers communicate satish kumar
2001-08-10 15:47 ` Randy.Dunlap [this message]
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=3B740216.FD13A444@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satish_shak@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.