1. 11 Dec, 2009 1 commit
  2. 30 Oct, 2009 1 commit
  3. 24 Sep, 2009 1 commit
  4. 03 Jul, 2009 1 commit
  5. 18 Jun, 2009 1 commit
  6. 12 Jun, 2009 1 commit
  7. 11 Jun, 2009 1 commit
  8. 21 May, 2009 1 commit
  9. 31 Jan, 2009 1 commit
  10. 08 Jan, 2009 1 commit
  11. 06 Jan, 2009 1 commit
  12. 02 Jan, 2009 2 commits
  13. 25 Dec, 2008 1 commit
    • Hendrik Brueckner's avatar
      [S390] s390/hvc_console: z/VM IUCV hypervisor console support · 44a01d5b
      Hendrik Brueckner authored
      
      
      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: default avatarHendrik Brueckner <brueckner@linux.vnet.ibm.com>
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      44a01d5b
  14. 19 Nov, 2008 1 commit
    • David Gibson's avatar
      powerpc: udbg-based backend for hvc_console · d5e54913
      David Gibson authored
      
      
      This adds a new backend for the hvc console based on the low-level
      udbg callbacks.  This effectively implements a working runtime console
      in terms of the simple udbg primitives.  This is kind of a hack -
      since udbg isn't something you really want to be using routinely - but
      it's really useful during bringup.
      
      This can be used to quickly implement a userspace-usable console while
      you're working on a proper driver for whatever console I/O device the
      hardware has.  Or, it can be used to avoid writing a full blown
      tty/console driver entirely for quick-and-dirty I/O hardware that will
      later be replaced by something else.
      Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      d5e54913
  15. 14 Nov, 2008 1 commit
  16. 30 Oct, 2008 2 commits
  17. 16 Oct, 2008 1 commit
  18. 13 Oct, 2008 1 commit
  19. 08 Aug, 2008 1 commit
  20. 25 Jul, 2008 2 commits
    • Christian Borntraeger's avatar
      virtio: console as a config option · 7721c494
      Christian Borntraeger authored
      
      
      I also added a small Kconfig change that allows the user to specify the
      virtio console in menuconfig.
      
      (Fixes to export symbols from Stephen Rothwell <sfr@canb.auug.org.au>)
      (Fixes for CONFIG_VIRTIO_CONSOLE=y vs CONFIG_VIRTIO=m from Christian himself)
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      7721c494
    • Christian Borntraeger's avatar
      hvc_console: rework setup to replace irq functions with callbacks · 611e097d
      Christian Borntraeger authored
      
      
      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: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
      611e097d
  21. 24 Jul, 2008 1 commit
  22. 22 Jul, 2008 7 commits
  23. 15 Jul, 2008 1 commit
  24. 13 Jun, 2008 1 commit
  25. 06 Jun, 2008 1 commit
  26. 04 Jun, 2008 1 commit
  27. 15 May, 2008 1 commit
  28. 29 Apr, 2008 1 commit
  29. 28 Apr, 2008 1 commit
    • David Brownell's avatar
      rtc: avoid legacy drivers with generic framework · c7500900
      David Brownell authored
      
      
      Kconfig tweaks to help reduce RTC configuration bugs, by avoiding
      legacy RTC drivers when the generic RTC framework is enabled:
      
       - If rtc-cmos is selected, disable the legacy rtc driver;
      
       - When using generic RTC on x86, enable rtc-cmos by default;
      
       - In the old "chardev RTC" section of Kconfig, add a comment
         warning people off these (seven) legacy RTC drivers when
         the generic framework is in use.
      
      People can still use the legacy drivers if they want (or need) to.
      
      This doesn't fix the broken dependencies for the legacy "CMOS" RTC driver.
      Ideally it would be a full list of platforms where it works, not a partial
      list of ones where it won't.  Or better yet, it would depend on a
      "HAVE_CMOS_RTC" flag defined by various platforms ...  surely there's a
      Kconfig style guideline lurking there.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Acked-by: default avatarAlessandro Zummo <a.zummo@towertech.it>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      c7500900
  30. 25 Apr, 2008 1 commit
  31. 20 Apr, 2008 1 commit