1. 03 7月, 2006 1 次提交
  2. 01 7月, 2006 1 次提交
  3. 30 6月, 2006 2 次提交
  4. 27 6月, 2006 1 次提交
  5. 26 6月, 2006 2 次提交
  6. 18 6月, 2006 5 次提交
  7. 26 5月, 2006 1 次提交
  8. 10 5月, 2006 2 次提交
  9. 07 5月, 2006 1 次提交
  10. 15 4月, 2006 2 次提交
  11. 10 4月, 2006 2 次提交
  12. 02 4月, 2006 1 次提交
  13. 29 3月, 2006 1 次提交
  14. 28 3月, 2006 1 次提交
  15. 26 3月, 2006 1 次提交
  16. 21 3月, 2006 9 次提交
  17. 20 2月, 2006 1 次提交
    • J
      [IRDA]: irda-usb bug fixes · 669d32a2
      Jean Tourrilhes 提交于
      This patch fixes 2 bugs in the USB-IrDA code.
      
      The first one is a buffer overrun in the RX path. We are now using
      IRDA_SKB_MAX_MTU when initializing the Rx URB.
      
      The second one is a potential stack recursion when unplugging the USB
      dongle.  It seems that first we get the Rx URB with a generic error
      code, and after a while the Rx URB comes again with a "disconnect"
      error code.  Since we are resubmitting the Rx URB immediately after
      receiving the first error one, we might enter an endless loop.
      
      When getting an error Rx URB, the patch defers the Rx URB resubmitting
      so that it gives us a chance to catch the disconnect one, in case the
      dongle has juts been unplugged.
      
      Tested against 2.6.16-rc2.
      
      Patch from Jean Tourrilhes
      Signed-off-by: NJean Tourrilhes <jt@hpl.hp.com>
      Signed-off-by: NSamuel Ortiz <samuel.ortiz@nokia.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      669d32a2
  18. 17 2月, 2006 1 次提交
  19. 11 1月, 2006 4 次提交
    • A
      [IRDA] DONGLE_OLD: remove dependency on non-existing symbol · 65e480ac
      Adrian Bunk 提交于
      Jean-Luc Leger <reiga@dspnet.fr.eu.org> reported this alternative 
      dependency on a non-existing symbol.
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      65e480ac
    • A
      [IRDA]: kill drivers/net/irda/sir_core.c · 214ad784
      Adrian Bunk 提交于
      EXPORT_SYMBOL's do nowadays belong to the files where the actual
      functions are.
      
      Moving the module_init/module_exit to the file with the actual functions
      has the advantage of saving a few bytes due to the removal of two
      functions.
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Acked-by: NJean Tourrilhes <jt@hpl.hp.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      214ad784
    • A
      [PATCH] TTY layer buffering revamp · 33f0f88f
      Alan Cox 提交于
      The API and code have been through various bits of initial review by
      serial driver people but they definitely need to live somewhere for a
      while so the unconverted drivers can get knocked into shape, existing
      drivers that have been updated can be better tuned and bugs whacked out.
      
      This replaces the tty flip buffers with kmalloc objects in rings. In the
      normal situation for an IRQ driven serial port at typical speeds the
      behaviour is pretty much the same, two buffers end up allocated and the
      kernel cycles between them as before.
      
      When there are delays or at high speed we now behave far better as the
      buffer pool can grow a bit rather than lose characters. This also means
      that we can operate at higher speeds reliably.
      
      For drivers that receive characters in blocks (DMA based, USB and
      especially virtualisation) the layer allows a lot of driver specific
      code that works around the tty layer with private secondary queues to be
      removed. The IBM folks need this sort of layer, the smart serial port
      people do, the virtualisers do (because a virtualised tty typically
      operates at infinite speed rather than emulating 9600 baud).
      
      Finally many drivers had invalid and unsafe attempts to avoid buffer
      overflows by directly invoking tty methods extracted out of the innards
      of work queue structs. These are no longer needed and all go away. That
      fixes various random hangs with serial ports on overflow.
      
      The other change in here is to optimise the receive_room path that is
      used by some callers. It turns out that only one ldisc uses receive room
      except asa constant and it updates it far far less than the value is
      read. We thus make it a variable not a function call.
      
      I expect the code to contain bugs due to the size alone but I'll be
      watching and squashing them and feeding out new patches as it goes.
      
      Because the buffers now dynamically expand you should only run out of
      buffering when the kernel runs out of memory for real.  That means a lot of
      the horrible hacks high performance drivers used to do just aren't needed any
      more.
      
      Description:
      
      tty_insert_flip_char is an old API and continues to work as before, as does
      tty_flip_buffer_push() [this is why many drivers dont need modification].  It
      does now also return the number of chars inserted
      
      There are also
      
      tty_buffer_request_room(tty, len)
      
      which asks for a buffer block of the length requested and returns the space
      found.  This improves efficiency with hardware that knows how much to
      transfer.
      
      and tty_insert_flip_string_flags(tty, str, flags, len)
      
      to insert a string of characters and flags
      
      For a smart interface the usual code is
      
          len = tty_request_buffer_room(tty, amount_hardware_says);
          tty_insert_flip_string(tty, buffer_from_card, len);
      
      More description!
      
      At the moment tty buffers are attached directly to the tty.  This is causing a
      lot of the problems related to tty layer locking, also problems at high speed
      and also with bursty data (such as occurs in virtualised environments)
      
      I'm working on ripping out the flip buffers and replacing them with a pool of
      dynamically allocated buffers.  This allows both for old style "byte I/O"
      devices and also helps virtualisation and smart devices where large blocks of
      data suddenely materialise and need storing.
      
      So far so good.  Lots of drivers reference tty->flip.*.  Several of them also
      call directly and unsafely into function pointers it provides.  This will all
      break.  Most drivers can use tty_insert_flip_char which can be kept as an API
      but others need more.
      
      At the moment I've added the following interfaces, if people think more will
      be needed now is a good time to say
      
       int tty_buffer_request_room(tty, size)
      
      Try and ensure at least size bytes are available, returns actual room (may be
      zero).  At the moment it just uses the flipbuf space but that will change.
      Repeated calls without characters being added are not cumulative.  (ie if you
      call it with 1, 1, 1, and then 4 you'll have four characters of space.  The
      other functions will also try and grow buffers in future but this will be a
      more efficient way when you know block sizes.
      
       int tty_insert_flip_char(tty, ch, flag)
      
      As before insert a character if there is room.  Now returns 1 for success, 0
      for failure.
      
       int tty_insert_flip_string(tty, str, len)
      
      Insert a block of non error characters.  Returns the number inserted.
      
       int tty_prepare_flip_string(tty, strptr, len)
      
      Adjust the buffer to allow len characters to be added.  Returns a buffer
      pointer in strptr and the length available.  This allows for hardware that
      needs to use functions like insl or mencpy_fromio.
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Cc: Paul Fulghum <paulkf@microgate.com>
      Signed-off-by: NHirokazu Takata <takata@linux-m32r.org>
      Signed-off-by: NSerge Hallyn <serue@us.ibm.com>
      Signed-off-by: NJeff Dike <jdike@addtoit.com>
      Signed-off-by: NJohn Hawkes <hawkes@sgi.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      33f0f88f
    • A
      [PATCH] drivers/net/irda/irport.c: cleanups · e7c368b7
      Adrian Bunk 提交于
      This patch contains the following cleanups:
      - make a needlessly global function static
      - remove the unneeded global function irport_probe
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Cc: Jeff Garzik <jgarzik@pobox.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e7c368b7
  20. 09 1月, 2006 1 次提交
    • J
      [PATCH] Eliminate __attribute__ ((packed)) warnings for gcc-4.1 · 6a878184
      Jan Blunck 提交于
      Since version 4.1 the gcc is warning about ignored attributes. This patch is
      using the equivalent attribute on the struct instead of on each of the
      structure or union members.
      
      GCC Manual:
        "Specifying Attributes of Types
      
         packed
          This attribute, attached to struct or union type definition, specifies
          that
          each member of the structure or union is placed to minimize the memory
          required. When attached to an enum definition, it indicates that the
          smallest integral type should be used.
      
          Specifying this attribute for struct and union types is equivalent to
          specifying the packed attribute on each of the structure or union
          members."
      Signed-off-by: NJan Blunck <jblunck@suse.de>
      Cc: Dave Jones <davej@codemonkey.org.uk>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6a878184