Skip to content
Snippets Groups Projects
  1. Sep 26, 2012
  2. Oct 22, 2010
  3. Mar 02, 2010
  4. Mar 24, 2009
  5. Oct 17, 2008
  6. Aug 14, 2008
    • Wolfgang Mües's avatar
      usb: auerswald: remove driver (obsolete) · 88d987d6
      Wolfgang Mües authored
      
      This patch removes the auerswald USB driver from the linux kernel
      2.6.26.
      
      This driver was included into the kernel mainly to connect to the ISDN
      framework. This was done in linux 2.4.x. For 2.6.x, due to the fragile
      and moving ISDN support, this connection was never realized, and the
      only use of this driver was for device configuration. In the age of DSL,
      the demand of ISDN support is getting very low.
      
      Meanwhile, with the advent of libusb, an userspace driver was done for
      the device configuration which works fine for linux and mac. (Thanks to
      the libusb developers!). The userspace driver is downloadable from the
      auerswald web site.
      
      So this driver is obsolete now and has to be removed. Many thanks to all
      developers which helped me to bring this driver up and working.
      
      Signed-off-by: default avatarWolfgang Muees <wolfgang@iksw-muees.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      88d987d6
  7. May 29, 2008
    • Matthew Garrett's avatar
      USB: Firmware loader driver for USB Apple iSight camera · 62d104d0
      Matthew Garrett authored
      Uninitialised Apple iSight drivers present with a distinctive USB ID.
      Once firmware has been uploaded, they disconnect and reconnect with a
      new ID. At this point they can be driven by the uvcvideo driver. As this
      is unique to the Apple cameras and not functionality shared by any other
      UVC devices, it makes sense to provide the firmware loading
      functionality in a separate driver. This driver will read an isight.fw
      file extracted from the Apple driver using the tools at
      http://bersace03.free.fr/ift/
      
       and upload it to the camera. It will also
      handle the case where the device loses its firmware during hibernation
      and must have it reloaded.
      
      Signed-off-by: default avatarMatthew Garrett <mjg@redhat.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      62d104d0
  8. Feb 23, 2007
  9. Feb 16, 2007
    • Greg Kroah-Hartman's avatar
      USB: Driver to charge USB blackberry devices · df23fa01
      Greg Kroah-Hartman authored
      
      A simple driver to turn on the charging capability of a USB BlackBerry
      device when it is plugged into the machine.  It does not bind to the
      device, so all userspace programs can still sync properly with it.
      
      Note, if CONFIG_USB_SUSPEND is enabled, it can play havoc with this
      device as the power to the port will be shut down.  This device id will
      have to be added to the global blacklist table when it is created.
      
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      df23fa01
  10. Dec 01, 2006
  11. Oct 17, 2006
  12. Sep 27, 2006
    • Tony Olech's avatar
      USB: ftdi-elan: client driver for ELAN Uxxx adapters · a5c66e4b
      Tony Olech authored
      
      This "ftdi-elan" module is one half of the "driver" for
      ELAN's Uxxx series adapters which are USB to PCMCIA CardBus
      adapters. Currently only the U132 adapter is available and
      it's module is called "u132-hcd".
      
      When the USB hot plug subsystem detects a Uxxx series adapter
      it should load this module.
      
      Upon a successful device probe() the jtag device file interface
      is created and the status workqueue started up.
      
      The jtag device file interface exists for the purpose of
      updating the firmware in the Uxxx series adapter, but as
      yet it had never been used.
      
      The status workqueue initializes the Uxxx and then sits there
      polling the Uxxx until a supported PCMCIA CardBus device is
      detected it will start the command and respond workqueues
      and then load the module that handles the device. This will
      initially be only the u132-hcd module. The status workqueue
      then just polls the Uxxx looking for card ejects.
      
      The command and respond workqueues implement a command
      sequencer for communicating with the firmware on the other
      side of the FTDI chip in the Uxxx. This "ftdi-elan" module
      exports some functions to interface with the sequencer.
      
      Note that this module is a USB client driver.
      
      Note that the "u132-hcd" module is a (cut-down OHCI)
      host controller.
      
      Thus we have a topology with the parent of a host controller
      being a USB client! This really stresses the USB subsystem
      semaphore/mutex handling in the module removal.
      
      Signed-off-by: default avatarTony Olech <tony.olech@elandigitalsystems.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      
      a5c66e4b
    • Steven Haigh's avatar
      USB: Add ADU support for Ontrak ADU devices · 03270634
      Steven Haigh authored
      
      This patch adds support for Ontrak ADU USB devices.
      
      Fixed for printk issues by Randy Dunlap <rdunlap@xenotime.net>
      
      Signed-off-by: default avatarSteven Haigh <netwiz@crc.id.au>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      03270634
    • Sean Young's avatar
      USB: Put phidgets driver in a sysfs class · 912b24c3
      Sean Young authored
      
      This patch creates a device class phidget and add the phidget drivers to 
      them.
      
      Signed-off-by: default avatarSean Young <sean@mess.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      912b24c3
    • Sean Young's avatar
      USB: Add driver for PhidgetMotorControl · d5176b41
      Sean Young authored
      
      This driver add support for the Phidgets Inc., MotorControl via sysfs. Also
      some minor fixes for the InterfaceKit.
      
      Signed-off-by: default avatarSean Young <sean@mess.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      d5176b41
  13. Jul 12, 2006
  14. Jun 21, 2006
  15. Nov 17, 2005
  16. Jul 12, 2005
    • Michael Hund's avatar
      [PATCH] USB: add ldusb driver · 2824bd25
      Michael Hund authored
      
      The following driver provides complete interrupt-in and interrupt-out
      reports (raw data) to a user program. Until now it uses the
      HIDIOCGDEVINFO ioctl call, because I don't know better :-(. Perhaps, it
      will be ok for you - and I will be happy, if you assign 8 minor numbers.
      
      I have tested it in several environments and it works very well for me.
      However, it has a problem with two or more devices at the same hub, if
      the two or more devices need 1 ms interrupt-in transfers. Unfortunately
      more than one interrupt-in transfer every ms isn't possible (ehci
      driver?). This is why the min_interrupt_in_interval and
      min_interrupt_out_interval are increased to 2 ms (see the corresponding
      module parameters). This way, I can use two devices simultaneously at
      the same hub.
      
      Signed-off-by: default avatarMichael Hund <mhund@ld-didactic.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      2824bd25
  17. Apr 16, 2005
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      v2.6.12-rc2
      1da177e4
Loading