1. 23 1月, 2011 5 次提交
    • R
      tty/serial: fix apbuart build · fed7bb32
      Randy Dunlap 提交于
      Fix build errors by selecting SERIAL_CORE:
      
      ERROR: "uart_register_driver" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_write_wakeup" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_update_timeout" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_get_divisor" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_get_baud_rate" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_add_one_port" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_unregister_driver" [drivers/tty/serial/apbuart.ko] undefined!
      ERROR: "uart_remove_one_port" [drivers/tty/serial/apbuart.ko] undefined!
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Daniel Hellstrom <daniel@gaisler.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      fed7bb32
    • P
      n_hdlc: fix read and write locking · 1035b63d
      Paul Fulghum 提交于
      Fix locking in read and write code of n_hdlc line discipline.
      
      2.6.36 replaced lock_kernel() with tty_lock().  The tty mutex is not
      dropped automatically when the thread sleeps like the BKL.  This results
      in a blocked read or write holding the tty mutex and stalling operations
      by other devices that use the tty mutex.
      
      A review of n_hdlc read and write code shows:
      1. neither BKL or tty mutex are required for correct operation
      2. read can block while read data is available if data is posted
         between availability check and call to interruptible_sleep_on()
      3. write does not set process state to TASK_INTERRUPTIBLE
         on each pass through the processing loop which can cause
         unneeded scheduling of the thread
      
      The unnecessary tty mutex references have been removed.
      
      Read changed to use same code as n_tty read
      for completing reads and blocking.
      
      Write corrected to set process state to TASK_INTERRUPTIBLE on each pass
      through processing loop.
      Signed-off-by: NPaul Fulghum <paulkf@microgate.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      1035b63d
    • P
      serial: unbreak billionton CF card · d0694e2a
      Pavel Machek 提交于
      Unbreak Billionton CF bluetooth card. This actually fixes a regression
      on zaurus.
      Signed-off-by: NPavel Machek <pavel@ucw.cz>
      Cc: stable <stable@kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      d0694e2a
    • K
      tty: use for_each_console() and WARN() on sysfs failures · a2a6a822
      Kay Sievers 提交于
      This fixes the build warnings in the tty code, and uses the proper
      function for iterating over the console devices.
      Signed-off-by: NKay Sievers <kay.sievers@vrfy.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      a2a6a822
    • D
      vt: fix issue when fbcon wants to takeover a second time. · c55c63c6
      Dave Airlie 提交于
      With framebuffer handover and multiple GPUs, we get into a
      position where the fbcon unbinds the vesafb framebuffer for GPU 1,
      but we still have a radeon framebuffer bound from GPU 0, so
      we don't unregister the console driver. Then when we tried to bind
      the new radeon framebuffer for GPU1 we never get to the bind
      call as we fail due to the console being registered already.
      
      This changes the return value to -EBUSY when the driver is
      already registered and continues to bind for -EBUSY.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      c55c63c6
  2. 22 1月, 2011 16 次提交
  3. 21 1月, 2011 19 次提交