From: htmldeveloper@gmail.com (Peter Teoh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Writing a USB driver for a non working device
Date: Wed, 12 Oct 2011 12:54:27 +0800 [thread overview]
Message-ID: <CAHnt0GW4UmJAug3dadnPzs6F9P3=Uwxh4EWrjk5L1ionb5x5GA@mail.gmail.com> (raw)
In-Reply-To: <CAA2WmRGiBQSB93Ao_5x0vAuLqv6PeUAPyQL9ntpf49_Yh23B-A@mail.gmail.com>
On Tue, Oct 11, 2011 at 11:42 PM, madav maddy <maddy.mdv007@gmail.com> wrote:
> Hi,
> I am newbie. For the better understanding of the USB, i have decided write a
> USB driver for the device for which it works in windows but not in linux.?So
> i have picked the Logitech USB headset.
> The background i have is ,i have studied the ldd usb drivers and written few
> dummy USB driver.
> Before i start implementing, i made some basic study
> - on connecting the device to my Ubuntu desktop, lsusb shows
> ? ? ?Bus 002 Device 065: ID 046d:0a01 Logitech, Inc. USB Headset
> on issuing dmesg.
> ? ?[550289.589037] usb 2-1.6: new full speed USB device using ehci_hcd and
> address 66
That is the vendor/product ID: 046d:0a01
And then normally u will use userspace USB API to open/read the device:
http://www.libusb.org/
libusb.sourceforge.net/doc/
>
> - so i believe there should be some driver already existing, is my
> understanding right?
> - if not, where can i start for implementing a new driver of my own?
> ? ? ? I think i need ?start doing some reverse engineering on windows using
> some usb logging tool, for the understanding of working of the device
>
> Thanks,
> Madav Raman
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
--
Regards,
Peter Teoh
prev parent reply other threads:[~2011-10-12 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 15:42 Writing a USB driver for a non working device madav maddy
2011-10-12 4:54 ` Peter Teoh [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='CAHnt0GW4UmJAug3dadnPzs6F9P3=Uwxh4EWrjk5L1ionb5x5GA@mail.gmail.com' \
--to=htmldeveloper@gmail.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).