All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Vishal Nandanwar
	<operational.people-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Alan Stern
	<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
	Linux USB <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux Docs <linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Platform driver x86
	<platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Need help to understand USB driver mechanism
Date: Thu, 21 Jun 2012 19:25:06 -0700	[thread overview]
Message-ID: <20120622022506.GA3726@kroah.com> (raw)
In-Reply-To: <CAKB833k1Q7LoJWxDp6AHdq5H=w=LeeeRQ3sRC_1zXcJ_Lp9mNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Fri, Jun 22, 2012 at 07:35:55AM +0530, Vishal Nandanwar wrote:
> Hi Alan,
> 
> Thanks for your reply. It really helps.
> 
> What approach one should use to learn the device drivers?

"Linux Device Drivers", third edition, free online.  Have you tried
that?

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-06-22  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 10:39 Need help to understand USB driver mechanism Vishal Nandanwar
     [not found] ` <CAKB833mPfX2U6_UA0Fr0CTw623gxCvcYPW3HvfVJWE1Xt7v-UQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-21 14:40   ` Alan Stern
     [not found]     ` <Pine.LNX.4.44L0.1206211036540.1164-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-06-22  2:05       ` Vishal Nandanwar
     [not found]         ` <CAKB833k1Q7LoJWxDp6AHdq5H=w=LeeeRQ3sRC_1zXcJ_Lp9mNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-22  2:25           ` Greg KH [this message]
2012-06-22  3:03             ` Vishal Nandanwar
2012-06-22 13:42               ` Greg KH
2012-06-22 13:48         ` Alan Stern

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=20120622022506.GA3726@kroah.com \
    --to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
    --cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=operational.people-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=platform-driver-x86-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.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 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.