20 Oct, 2008

1 commit


18 Oct, 2008

3 commits


10 Oct, 2008

1 commit


24 Sep, 2008

1 commit


17 Sep, 2008

2 commits


14 Aug, 2008

2 commits

  • this mentions a new deadlock due to advanced power management.

    Signed-off-by: Oliver Neukum
    Signed-off-by: Greg Kroah-Hartman

    Oliver Neukum
     
  • 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: Wolfgang Muees
    Signed-off-by: Greg Kroah-Hartman

    Wolfgang Mües
     

27 Jul, 2008

1 commit


22 Jul, 2008

3 commits

  • This patch (as1109b) makes USB-Persist more resilient to errors. With
    the current code, if a normal resume fails, it's an unrecoverable
    error. With the patch, if a normal resume fails (and if the device is
    enabled for USB-Persist) then a reset-resume is tried.

    This fixes the problem reported in Bugzilla #10977.

    Signed-off-by: Alan Stern
    Signed-off-by: Greg Kroah-Hartman

    Alan Stern
     
  • Teach "gadget serial" to use the new abstracted (and bugfixed) TTY glue,
    and remove all the orignal tangled-up code. Update the documentation
    accordingly. This is a net object code shrink and cleanup; it should
    make it a lot easier to see how the TTY glue should accomodate updates
    to the TTY layer, be bugfixed, etc.

    Notable behavior changes include: it can now support getty even when
    there's no USB connection; it fits properly into the mdev/udev world;
    and RX handling is better (throttling works, and low latency).

    Configurations with scripts setting up the /dev/ttygserial device node
    (with "experimental" major number) may want to change that to be a
    symlink pointing to the /dev/ttyGS0 file, as a migration aid; else,
    just switch entirely over to mdev/udev.

    Signed-off-by: David Brownell
    Signed-off-by: Greg Kroah-Hartman

    David Brownell
     
  • The driver was removed before kernel 2.6.0

    Signed-off-by: Adrian Bunk
    Signed-off-by: Greg Kroah-Hartman

    Adrian Bunk
     

25 Apr, 2008

5 commits


11 Mar, 2008

1 commit


02 Feb, 2008

2 commits

  • G_PRINTER: Adds a USB printer gadget driver for use in printer firmware.

    This adds a USB printer gadget driver for use in printer firmware.
    The printer gadget channels data between the USB host and a userspace
    program driving the print engine. The user space program reads and
    writes the device file /dev/g_printer to receive or send printer data.
    It can use ioctl calls to the device file to get or set printer status.

    Signed-off-by: Craig W. Nadler
    Signed-off-by: David Brownell
    Signed-off-by: Greg Kroah-Hartman

    Craig W. Nadler
     
  • Signed-off-by: Alain Degreffe
    Cc: Alan Cox
    Cc: Oliver Neukum
    Signed-off-by: Greg Kroah-Hartman

    Alain Degreffe
     

29 Nov, 2007

1 commit

  • This patch (as1014) was partly written by Tilman Schmidt. It
    clarifies the USB power-management documentation by explaining that
    when a disconnect occurs, a suspend method call might not be followed
    by either a resume or a reset_resume call.

    Signed-off-by: Alan Stern
    Signed-off-by: Tilman Schmidt
    Signed-off-by: Greg Kroah-Hartman

    Alan Stern
     

20 Oct, 2007

1 commit


13 Oct, 2007

4 commits


13 Jul, 2007

3 commits

  • This patch updates some of the documentation about DMA buffer management
    for USB, and ways to avoid extra copying. Our understanding of the issues
    has improved over time.

    - Most drivers should *avoid* the dma-coherent allocators. There are
    a few exceptions (like the HID driver).

    - Some methods are currently commented out; it seems folk writing
    USB drivers aren't doing performance tuning at that level yet.

    - Just avoid highmem; there's no good way to pass an "I can do highmem
    DMA" capability through a driver stack. This is easy, everything
    already avoids highmem. But it'd be nice if x86_32 systems with much
    physical memory could use it directly with network adapters and mass
    storage devices. (Patch, anyone?)

    Signed-off-by: David Brownell
    Signed-off-by: Greg Kroah-Hartman

    David Brownell
     
  • This patch (as920) adds an extra level of protection to the
    USB-Persist facility. Now it will apply by default only to hubs; for
    all other devices the user must enable it explicitly by setting the
    power/persist device attribute.

    The disconnect_all_children() routine in hub.c has been removed and
    its code placed inline. This is the way it was originally as part of
    hub_pre_reset(); the revised usage in hub_reset_resume() is
    sufficiently different that the code can no longer be shared.
    Likewise, mark_children_for_reset() is now inline as part of
    hub_reset_resume(). The end result looks much cleaner than before.

    The sysfs interface is updated to add the new attribute file, and
    there are corresponding documentation updates.

    Signed-off-by: Alan Stern
    Signed-off-by: Greg Kroah-Hartman

    Alan Stern
     
  • This patch (as886) adds the controversial USB-persist facility,
    allowing USB devices to persist across a power loss during system
    suspend.

    The facility is controlled by a new Kconfig option (with appropriate
    warnings about the potential dangers); when the option is off the
    behavior will remain the same as it is now. But when the option is
    on, people will be able to use suspend-to-disk and keep their USB
    filesystems intact -- something particularly valuable for small
    machines where the root filesystem is on a USB device!

    Signed-off-by: Alan Stern
    Signed-off-by: Greg Kroah-Hartman

    Alan Stern
     

09 May, 2007

1 commit


05 May, 2007

1 commit


28 Apr, 2007

1 commit

  • This patch adds a new text API, codenamed '1u', which captures more URB
    fields than old '1t' interface did. Also the '1u' text API is compatible
    with the future "bus zero" extension.

    Signed-off-by: Pete Zaitcev
    Acked-by: Alan Stern
    Signed-off-by: Greg Kroah-Hartman

    Pete Zaitcev
     

08 Feb, 2007

2 commits

  • This patch adds a new, "binary" API in addition to the old, text API usbmon
    had before. The new API allows for less CPU use, and it allows to capture
    all data from a packet where old API only captured 32 bytes at most. There
    are some limitations and conditions to this, e.g. in case someone constructs
    a URB with 1GB of data, it's not likely to be captured, because even the
    huge buffers of the new reader are finite. Nonetheless, I expect this new
    capability to capture all data for all real life scenarios.

    The downside is, a special user mode application is required where cat(1)
    worked before. I have sample code at http://people.redhat.com/zaitcev/linux/
    and Paolo Abeni is working on patching libpcap.

    This patch was initially written by Paolo and later I tweaked it, and
    we had a little back-and-forth. So this is a jointly authored patch, but
    I am submitting this I am responsible for the bugs.

    Signed-off-by: Paolo Abeni
    Signed-off-by: Pete Zaitcev
    Signed-off-by: Greg Kroah-Hartman

    Pete Zaitcev
     
  • Update /proc/bus/usb/devices output to report active altsettings.

    Signed-off-by: David Brownell
    Signed-off-by: Greg Kroah-Hartman

    David Brownell
     

24 Jan, 2007

1 commit


06 Jan, 2007

1 commit


30 Nov, 2006

2 commits