1. 27 Apr, 2007 1 commit
  2. 25 Apr, 2007 2 commits
  3. 24 Apr, 2007 1 commit
    • Dan Williams's avatar
      usb-net/pegasus: fix pegasus carrier detection · c43c49bd
      Dan Williams authored
      Broken by 4a1728a2
      
       which switched the
      return semantics of read_mii_word() but didn't fix usage of
      read_mii_word() to conform to the new semantics.
      
      Setting carrier to off based on the NO_CARRIER flag is also incorrect as
      that flag only triggers on TX failure and therefore isn't correct when
      no frames are being transmitted.  Since there is already a 2*HZ MII
      carrier check going on, defer to that.
      
      Add a TRUST_LINK_STATUS feature flag for adapters where the LINK_STATUS
      flag is actually correct, and use that rather than the NO_CARRIER flag.
      
      Signed-off-by: default avatarDan Williams <dcbw@redhat.com>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
      c43c49bd
  4. 07 Dec, 2006 1 commit
  5. 01 Dec, 2006 1 commit
  6. 22 Nov, 2006 1 commit
  7. 05 Oct, 2006 1 commit
    • David Howells's avatar
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells authored
      
      
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      
      Signed-Off-By: default avatarDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  8. 28 Sep, 2006 1 commit
    • Petko Manolov's avatar
      USB: Pegasus driver failing for ADMtek 8515 network device · 37cf3477
      Petko Manolov authored
      Address http://bugzilla.kernel.org/show_bug.cgi?id=7126
      
      
      
      Attempting to read the ethernet ID directly from the eeprom somehow
      confuses ADM8515.  Subsequent read requests to either the eeprom or the MII
      fail as well.  Didn't dig much deeper, though.  For example ADM8513 does
      not experience this problem.
      
      I used the fact that at power up the device is reading its ID automatically
      (not true for older Pegasus based devices) and put it in the Ethernet ID
      registers.  So now the driver uses get_registers() instead of
      read_eprom_word() if the device is Pegasus_II based one.  Tested it with
      all (Pegasus and Pegasus_II) gadgets i have and everything seems ok.
      
      Cc: <jogeedaklown@yahoo.com>
      Cc: David Brownell <david-b@pacbell.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      37cf3477
  9. 27 Sep, 2006 1 commit
    • Pete Zaitcev's avatar
      USB: Dealias -110 code (more complete) · 38e2bfc9
      Pete Zaitcev authored
      
      
      The purpose of this patch is to split off the case when a device does
      not reply on the lower level (which is reported by HC hardware), and
      a case when the device accepted the request, but does not reply at
      upper level. This redefinition allows to diagnose issues easier,
      without asking the user if the -110 happened "immediately".
      
      The usbmon splits such cases already thanks to its timestamp, but
      it's not always available.
      
      I adjusted all drivers which I found affected (by searching for "urb").
      Out of tree drivers may suffer a little bit, but I do not expect much
      breakage. At worst they may print a few messages.
      
      Signed-off-by: default avatarPete Zaitcev <zaitcev@redhat.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      38e2bfc9
  10. 21 Jun, 2006 1 commit
  11. 09 May, 2006 1 commit
  12. 14 Apr, 2006 1 commit
  13. 20 Mar, 2006 1 commit
  14. 04 Jan, 2006 2 commits
  15. 17 Nov, 2005 1 commit
  16. 28 Oct, 2005 1 commit
    • David Brownell's avatar
      [PATCH] usb_interface power state · db690874
      David Brownell authored
      
      
      This updates the handling of power state for USB interfaces.
      
        - Formalizes an existing invariant:  interface "power state" is a boolean:
          ON when I/O is allowed, and FREEZE otherwise.  It does so by defining
          some inlined helpers, then using them.
      
        - Adds a useful invariant:  the only interfaces marked active are those
          bound to non-suspended drivers.  Later patches build on this invariant.
      
        - Simplifies the interface driver API (and removes some error paths) by
          removing the requirement that they record power state changes during
          suspend and resume callbacks.  Now usbcore does that.
      
      A few drivers were simplified to address that last change.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      
       drivers/usb/core/hub.c       |   33 +++++++++------------
       drivers/usb/core/message.c   |    1
       drivers/usb/core/usb.c       |   65 +++++++++++++++++++++++++++++++++----------
       drivers/usb/core/usb.h       |   18 +++++++++++
       drivers/usb/input/hid-core.c |    2 -
       drivers/usb/misc/usbtest.c   |   10 ------
       drivers/usb/net/pegasus.c    |    2 -
       drivers/usb/net/usbnet.c     |    2 -
       8 files changed, 85 insertions(+), 48 deletions(-)
      db690874
  17. 22 Sep, 2005 1 commit
  18. 08 Sep, 2005 1 commit
    • Alan Stern's avatar
      [PATCH] USB: URB_ASYNC_UNLINK flag removed from the kernel · b375a049
      Alan Stern authored
      
      
      29 July 2005, Cambridge, MA:
      
      This afternoon Alan Stern submitted a patch to remove the URB_ASYNC_UNLINK
      flag from the Linux kernel.  Mr. Stern explained, "This flag is a relic
      from an earlier, less-well-designed system.  For over a year it hasn't
      been used for anything other than printing warning messages."
      
      An anonymous spokesman for the Linux kernel development community
      commented, "This is exactly the sort of thing we see happening all the
      time.  As the kernel evolves, support for old techniques and old code can
      be jettisoned and replaced by newer, better approaches.  Proprietary
      operating systems do not have the freedom or flexibility to change so
      quickly."
      
      Mr. Stern, a staff member at Harvard University's Rowland Institute who
      works on Linux only as a hobby, noted that the patch (labelled as548) did
      not update two files, keyspan.c and option.c, in the USB drivers' "serial"
      subdirectory.  "Those files need more extensive changes," he remarked.
      "They examine the status field of several URBs at times when they're not
      supposed to.  That will need to be fixed before the URB_ASYNC_UNLINK flag
      is removed."
      
      Greg Kroah-Hartman, the kernel maintainer responsible for overseeing all
      of Linux's USB drivers, did not respond to our inquiries or return our
      calls.  His only comment was "Applied, thanks."
      
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      b375a049
  19. 29 Jul, 2005 1 commit
  20. 26 Jun, 2005 1 commit
  21. 26 Apr, 2005 1 commit
  22. 18 Apr, 2005 1 commit
    • David Brownell's avatar
      [PATCH] usb suspend updates (interface suspend) · 27d72e85
      David Brownell authored
      
      
      This is the first of a few installments of PM API updates to match the
      recent switch to "pm_message_t".  This installment primarily affects
      USB device drivers (for USB interfaces), and it changes the handful of
      drivers which currently implement suspend methods:
      
          - <linux/usb.h> and usbcore, signature change
      
          - Some drivers only changed the signature, net effect this just
            shuts up "sparse -Wbitwise":
      	* hid-core
      	* stir4200
      
          - Two network drivers did that, and also grew slightly more
            featureful suspend code ... they now properly shut down
            their activities.  (As should stir4200...)
      	* pegasus
      	* usbnet
      
      Note that the Wake-On-Lan (WOL) support in pegasus doesn't yet work; looks
      to me like it's missing a request to turn it on, vs just configuring it.
      The ASIX code in usbnet also has WOL hooks that are ready to use; untested.
      
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      
      Index: gregkh-2.6/drivers/net/irda/stir4200.c
      ===================================================================
      27d72e85
  23. 16 Apr, 2005 1 commit
    • 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!
      1da177e4