1. 22 1月, 2008 1 次提交
    • A
      keyspan: fix oops · a5569a56
      Alan Cox 提交于
      If we get a data URB back from the hardware after we have put the tty to
      bed we go kaboom.  Fortunately all we need to do is process the URB without
      trying to ram its contents down the throat of an ex-tty.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: Linus Torvalds <torvalds@akpm@linux-foundation.org>
      a5569a56
  2. 30 11月, 2007 1 次提交
    • A
      revert "keyspan: init termios properly" · f78ba157
      Andrew Morton 提交于
      Revert 7eea4364.
      
      Lucy said:
      
        This patch will work with the 19HS but WILL BREAK all other Keyspan
        adapters.  It will take me a few days to get to looking at a correct fix but
        that keyspan_send_setup(port, 1) (and the '1' is the important part) must
        happen once when the port is first opened.  The cflag can just be set to
        whatever the normal default is for your serial environment.
      
      So revert this again pending the proper fix.
      
      Cc: Borislav Petkov <bbpetkov@yahoo.de>
      Cc: Greg KH <greg@kroah.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Lucy McCoy <lucy@keyspan.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f78ba157
  3. 15 11月, 2007 1 次提交
  4. 26 10月, 2007 1 次提交
  5. 13 7月, 2007 2 次提交
  6. 08 2月, 2007 1 次提交
    • R
      fix for bugzilla #7544 (keyspan USB-to-serial converter) · fdcba53e
      Rainer Weikusat 提交于
      At least the Keyspan USA-19HS USB-to-serial converter supports
      two different configurations, one where the input endpoints
      have interrupt transfer type and one where they are bulk endpoints.
      The default UHCI configuration uses the interrupt input endpoints.
      The keyspan driver, OTOH, assumes that the device has only bulk
      endpoints (all URBs are initialized by calling usb_fill_bulk_urb
      in keyspan.c/ keyspan_setup_urb). This causes the interval field
      of the input URBs to have a value of zero instead of one, which
      'accidentally' worked with Linux at least up to 2.6.17.11 but
      stopped to with 2.6.18, which changed the UHCI support code handling
      URBs for interrupt endpoints. The patch below modifies to driver to
      initialize its input URBs either as interrupt or as bulk URBs,
      depending on the transfertype contained in the associated endpoint
      descriptor (only tested with the default configuration) enabling
      the driver to again receive data from the serial converter.
      
      Greg K-H reworked the patch.
      Signed-off-by: NRainer Weikusat <rweikusat@sncag.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      fdcba53e
  7. 09 12月, 2006 1 次提交
    • A
      [PATCH] tty: switch to ktermios · 606d099c
      Alan Cox 提交于
      This is the grungy swap all the occurrences in the right places patch that
      goes with the updates.  At this point we have the same functionality as
      before (except that sgttyb() returns speeds not zero) and are ready to
      begin turning new stuff on providing nobody reports lots of bugs
      
      If you are a tty driver author converting an out of tree driver the only
      impact should be termios->ktermios name changes for the speed/property
      setting functions from your upper layers.
      
      If you are implementing your own TCGETS function before then your driver
      was broken already and its about to get a whole lot more painful for you so
      please fix it 8)
      
      Also fill in c_ispeed/ospeed on init for most devices, although the current
      code will do this for you anyway but I'd like eventually to lose that extra
      paranoia
      
      [akpm@osdl.org: bluetooth fix]
      [mp3@de.ibm.com: sclp fix]
      [mp3@de.ibm.com: warning fix for tty3270]
      [hugh@veritas.com: fix tty_ioctl powerpc build]
      [jdike@addtoit.com: uml: fix ->set_termios declaration]
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NMartin Peschke <mp3@de.ibm.com>
      Acked-by: NPeter Oberparleiter <oberpar@de.ibm.com>
      Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Signed-off-by: NJeff Dike <jdike@addtoit.com>
      Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      606d099c
  8. 02 12月, 2006 1 次提交
  9. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      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: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  10. 13 7月, 2006 1 次提交
  11. 01 7月, 2006 1 次提交
  12. 22 6月, 2006 1 次提交
  13. 21 3月, 2006 1 次提交
  14. 09 9月, 2005 1 次提交
  15. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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