Skip to content
Snippets Groups Projects
  1. Nov 17, 2010
  2. Jun 30, 2010
  3. May 17, 2010
  4. May 10, 2010
  5. Feb 17, 2010
  6. Feb 12, 2010
  7. Oct 13, 2009
  8. Sep 02, 2009
  9. Sep 01, 2009
  10. Jul 12, 2009
  11. Jul 05, 2009
  12. Jun 19, 2009
  13. Apr 17, 2009
  14. Jan 08, 2009
  15. Jan 07, 2009
  16. Dec 19, 2008
  17. Nov 16, 2008
  18. Oct 27, 2008
  19. Oct 20, 2008
  20. Sep 24, 2008
  21. Sep 03, 2008
  22. Aug 07, 2008
  23. Mar 28, 2008
  24. Oct 10, 2007
  25. Jul 30, 2007
  26. May 09, 2007
  27. Apr 27, 2007
  28. Apr 25, 2007
  29. Apr 24, 2007
    • 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
  30. Dec 07, 2006
  31. Dec 01, 2006
  32. Nov 22, 2006
  33. Oct 05, 2006
    • 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
  34. Sep 28, 2006
    • 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
  35. Sep 27, 2006
    • 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
  36. Jun 21, 2006
Loading