1. 25 12月, 2008 1 次提交
    • H
      [S390] s390/hvc_console: z/VM IUCV hypervisor console support · 44a01d5b
      Hendrik Brueckner 提交于
      This patch introduces a new hypervisor console (HVC) back-end that provides
      terminal access over the z/VM inter-user communication vehicle (IUCV).
      
      The z/VM IUCV communication is independent of the regular tcp/ip network
      and allows access even if there is no network connection between two
      z/VM guest virtual machines.
      The z/VM IUCV hypervisor console back-end helps the user to access a
      z/VM guest virtual machine that lacks of network connectivity; and thus,
      provides a "full-screen" terminal alternative to 3215/3270 terminal sessions.
      
      Use the hvc_iucv=[0..8] kernel boot parameter to specify the number of
      HVC terminals using a z/VM IUCV back-end.
      
      A recent version of the s390-tools package is required to establish a
      terminal connection to a z/VM IUCV hypervisor console back-end.
      Signed-off-by: NHendrik Brueckner <brueckner@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      44a01d5b
  2. 30 10月, 2008 2 次提交
  3. 14 10月, 2008 2 次提交
  4. 08 8月, 2008 1 次提交
  5. 26 7月, 2008 1 次提交
  6. 25 7月, 2008 2 次提交
    • C
      hvc_console: rework setup to replace irq functions with callbacks · 611e097d
      Christian Borntraeger 提交于
      This patch tries to change hvc_console to not use request_irq/free_irq if
      the backend does not use irqs. This allows virtio_console to use hvc_console
      without having a linker reference to request_irq/free_irq.
      
      In addition, together with patch 2/3 it improves the performance for virtio
      console input. (an earlier version of this patch was tested by Yajin on lguest)
      
      The irq specific code is moved to hvc_irq.c and selected by the drivers that
      use irqs (System p, System i, XEN).
      
      I replaced "int irq" with the opaque "int data". The request_irq and
      free_irq calls are replaced with notifier_add and notifier_del. I have also
      changed the code a bit to call the notifier_add and notifier_del inside the
      spinlock area as the callbacks are found via hp->ops.
      
      Changes since last version:
      o remove ifdef
      o reintroduce "irq_requested" as "notified"
      o cleanups, sparse..
      
      I did not move the timer based polling into a separate polling scheme. I
      played with several variants, but it seems we need to sleep/schedule in
      a thread even for irq based consoles, as there are throttleing and buffer
      size constraints.
      
      I also kept hvc_struct defined in hvc_console.h so that hvc_irq.c can access
      the irq_requested element.
      
      Feedback is appreciated. virtio_console is currently the only available console
      for kvm on s390. I plan to push this change as soon as all affected parties
      agree on it. I would love to get test results from System p, Xen etc.
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      611e097d
    • Y
      drivers/char: remove old broken Cobalt LCD driver · 18b095d4
      Yoichi Yuasa 提交于
      Remove old broken Cobalt LCD driver.
      Signed-off-by: NYoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
      Acked-by: NRalf Baechle <ralf@linux-mips.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      18b095d4
  7. 23 7月, 2008 1 次提交
  8. 15 7月, 2008 1 次提交
  9. 14 7月, 2008 1 次提交
    • D
      drm: reorganise drm tree to be more future proof. · c0e09200
      Dave Airlie 提交于
      With the coming of kernel based modesetting and the memory manager stuff,
      the everything in one directory approach was getting very ugly and
      starting to be unmanageable.
      
      This restructures the drm along the lines of other kernel components.
      
      It creates a drivers/gpu/drm directory and moves the hw drivers into
      subdirectores. It moves the includes into an include/drm, and
      sets up the unifdef for the userspace headers we should be exporting.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      c0e09200
  10. 04 6月, 2008 1 次提交
  11. 25 4月, 2008 1 次提交
  12. 08 2月, 2008 1 次提交
  13. 07 2月, 2008 1 次提交
    • S
      [POWERPC] Xilinx: hwicap driver · ef141a0b
      Stephen Neuendorffer 提交于
      This includes code for new fifo-based xps_hwicap in addition to the
      older opb_hwicap, which has a significantly different interface.  The
      common code between the two drivers is largely shared.
      
      Significant differences exists between this driver and what is
      supported in the EDK drivers.  In particular, most of the
      architecture-specific code for reconfiguring individual FPGA resources
      has been removed.  This functionality is likely better provided in a
      user-space support library.  In addition, read and write access is
      supported.  In addition, although the xps_hwicap cores support
      interrupt-driver mode, this driver only supports polled operation, in
      order to make the code simpler, and since the interrupt processing
      overhead is likely to slow down the throughput under Linux.
      Signed-off-by: NStephen Neuendorffer <stephen.neuendorffer@xilinx.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      ef141a0b
  14. 25 1月, 2008 1 次提交
    • F
      nozomi driver · 20fd1e3b
      Frank Seidel 提交于
      This is a driver to control the cardbus wireless data card that works on
      3g networks.
      
      Greg Kroah-Hartman <gregkh@suse.de> did the initial driver cleanup.
      Thanks to Arnaud Patard <apatard@mandriva.com> for help with bugfixing.
      Thanks to Alan Cox for a lot of tty fixes.
      Thanks to Satyam Sharma <satyam@infradead.org> for fixing buildbreakage.
      Thanks to Frank Seidel <fseidel@suse.de> for a lot of bugfixes and
      rewriting to make it a sane Linux driver
      Thanks to Jiri Slaby <jirislaby@gmail.com> for a lot bugfixes, cleanups
      and rewrites that make it much more readable.
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: NFrank Seidel <fseidel@suse.de>
      Signed-off-by: NJiri Slaby <jirislaby@gmail.com>
      20fd1e3b
  15. 23 10月, 2007 2 次提交
  16. 09 10月, 2007 1 次提交
  17. 30 7月, 2007 1 次提交
    • W
      [WATCHDOG] Fix pcwd_init_module crash · 647e50f3
      Wim Van Sebroeck 提交于
      Fix for the problem detected by Ingo Molnar:
      enabling CONFIG_PCWATCHDOG=y crashes bzImage bootup.
      
      The reason for this can be found in drivers/makefile
      We first do:
      obj-y                           += char/
      and later we do:
      obj-y                           += base/ block/ misc/ mfd/ net/ media/
      
      So if we put a platform or isa or usb bus driver in char/watchdog
      (which is called from the Makefile in drivers/char/Makefile)
      then we didn't have the different device drivers initialized yet
      (they are in drivers/base and drivers/usb and ...)
      
      This fix makes sure that we compile the watchdog drivers after
      drivers/base, drivers/misc, drivers/pci and drivers/usb.
      We also do the compile after hwmon because in the future the
      watchdog temperature support will use the hwmon system.
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      647e50f3
  18. 25 7月, 2007 1 次提交
  19. 22 7月, 2007 1 次提交
  20. 20 7月, 2007 1 次提交
  21. 18 7月, 2007 1 次提交
  22. 17 7月, 2007 1 次提交
    • M
      Audit: add TTY input auditing · 522ed776
      Miloslav Trmac 提交于
      Add TTY input auditing, used to audit system administrator's actions.  This is
      required by various security standards such as DCID 6/3 and PCI to provide
      non-repudiation of administrator's actions and to allow a review of past
      actions if the administrator seems to overstep their duties or if the system
      becomes misconfigured for unknown reasons.  These requirements do not make it
      necessary to audit TTY output as well.
      
      Compared to an user-space keylogger, this approach records TTY input using the
      audit subsystem, correlated with other audit events, and it is completely
      transparent to the user-space application (e.g.  the console ioctls still
      work).
      
      TTY input auditing works on a higher level than auditing all system calls
      within the session, which would produce an overwhelming amount of mostly
      useless audit events.
      
      Add an "audit_tty" attribute, inherited across fork ().  Data read from TTYs
      by process with the attribute is sent to the audit subsystem by the kernel.
      The audit netlink interface is extended to allow modifying the audit_tty
      attribute, and to allow sending explanatory audit events from user-space (for
      example, a shell might send an event containing the final command, after the
      interactive command-line editing and history expansion is performed, which
      might be difficult to decipher from the TTY input alone).
      
      Because the "audit_tty" attribute is inherited across fork (), it would be set
      e.g.  for sshd restarted within an audited session.  To prevent this, the
      audit_tty attribute is cleared when a process with no open TTY file
      descriptors (e.g.  after daemon startup) opens a TTY.
      
      See https://www.redhat.com/archives/linux-audit/2007-June/msg00000.html for a
      more detailed rationale document for an older version of this patch.
      
      [akpm@linux-foundation.org: build fix]
      Signed-off-by: NMiloslav Trmac <mitr@redhat.com>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Paul Fulghum <paulkf@microgate.com>
      Cc: Casey Schaufler <casey@schaufler-ca.com>
      Cc: Steve Grubb <sgrubb@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      522ed776
  23. 08 5月, 2007 1 次提交
  24. 10 2月, 2007 1 次提交
  25. 07 2月, 2007 1 次提交
  26. 09 12月, 2006 1 次提交
  27. 04 12月, 2006 1 次提交
  28. 04 10月, 2006 1 次提交
  29. 30 9月, 2006 1 次提交
  30. 27 9月, 2006 1 次提交
  31. 13 7月, 2006 1 次提交
  32. 07 7月, 2006 1 次提交
  33. 28 6月, 2006 3 次提交
  34. 27 6月, 2006 1 次提交