acrn-kernel/drivers/usb
David S. Miller 462aae65f6 [USB]: Make early handoff a final fixup instead of a header one.
At header fixup time, it is not yet legal to ioremap() PCI
device registers, yet that is what this quirk code needs to
do.

Signed-off-by: David S. Miller <davem@davemloft.net>
2005-11-04 11:17:24 -08:00
..
atm
class [PATCH] USB: cdc-acm patch to use kzalloc 2005-10-28 16:47:49 -07:00
core USB: fix up some odd parts due to partial merges 2005-10-28 19:59:31 -07:00
gadget Create platform_device.h to contain all the platform device details. 2005-10-29 19:07:23 +01:00
host [USB]: Make early handoff a final fixup instead of a header one. 2005-11-04 11:17:24 -08:00
image [PATCH] mdc800: remove embrions of C++ exceptions 2005-10-28 16:47:50 -07:00
input [PATCH] Typo fix: dot after newline in printk strings 2005-10-30 17:37:20 -08:00
media
misc [PATCH] Use sg_set_buf/sg_init_one where applicable 2005-10-30 11:19:43 +11:00
mon [PATCH] USB: convert usbmon to use usb notifiers 2005-10-28 16:47:46 -07:00
net [PATCH] USB: fix correct wording in drivers/usb/net/KConfig 2005-10-28 16:47:52 -07:00
serial [PATCH] USB: add nokia_dku2 driver 2005-10-28 16:47:53 -07:00
storage [PATCH] USB Storage: Expand range of Freecom unusual_devs entry 2005-10-28 16:47:50 -07:00
Kconfig
Makefile [PATCH] USB: delete the bluetty driver 2005-10-28 16:47:47 -07:00
README
usb-skeleton.c

README

To understand all the Linux-USB framework, you'll use these resources:

    * This source code.  This is necessarily an evolving work, and
      includes kerneldoc that should help you get a current overview.
      ("make pdfdocs", and then look at "usb.pdf" for host side and
      "gadget.pdf" for peripheral side.)  Also, Documentation/usb has
      more information.

    * The USB 2.0 specification (from www.usb.org), with supplements
      such as those for USB OTG and the various device classes.
      The USB specification has a good overview chapter, and USB
      peripherals conform to the widely known "Chapter 9".

    * Chip specifications for USB controllers.  Examples include
      host controllers (on PCs, servers, and more); peripheral
      controllers (in devices with Linux firmware, like printers or
      cell phones); and hard-wired peripherals like Ethernet adapters.

    * Specifications for other protocols implemented by USB peripheral
      functions.  Some are vendor-specific; others are vendor-neutral
      but just standardized outside of the www.usb.org team.

Here is a list of what each subdirectory here is, and what is contained in
them.

core/		- This is for the core USB host code, including the
		  usbfs files and the hub class driver ("khubd").

host/		- This is for USB host controller drivers.  This
		  includes UHCI, OHCI, EHCI, and others that might
		  be used with more specialized "embedded" systems.

gadget/		- This is for USB peripheral controller drivers and
		  the various gadget drivers which talk to them.


Individual USB driver directories.  A new driver should be added to the
first subdirectory in the list below that it fits into.

image/		- This is for still image drivers, like scanners or
		  digital cameras.
input/		- This is for any driver that uses the input subsystem,
		  like keyboard, mice, touchscreens, tablets, etc.
media/		- This is for multimedia drivers, like video cameras,
		  radios, and any other drivers that talk to the v4l
		  subsystem.
net/		- This is for network drivers.
serial/		- This is for USB to serial drivers.
storage/	- This is for USB mass-storage drivers.
class/		- This is for all USB device drivers that do not fit
		  into any of the above categories, and work for a range
		  of USB Class specified devices. 
misc/		- This is for all USB device drivers that do not fit
		  into any of the above categories.