26 Jul, 2011

1 commit


19 Mar, 2010

1 commit

  • This reverts commit eec9fe7d1ab4a0dfac4cb43047a7657fffd0002f.

    Ari writes as the reason this should be reverted:
    The problems with this patch include:
    1. There's at least one subtlety I overlooked - switching
    between X servers (i.e. from one X VT to another) still requires
    the cooperation of both X servers. I was assuming that KMS
    eliminated this.
    2. It hasn't been tested at all (no X server patch exists which
    uses the new mode).

    As he was the original author of the patch, I'll revert it.

    Cc: Ari Entlich
    Cc: Alan Cox
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

03 Mar, 2010

1 commit

  • This new VT mode (VT_PROCESS_AUTO) does everything that VT_PROCESS does
    except that it doesn't wait for a VT_RELDISP ioctl before switching
    away from a VT with that mode.

    If the X server eventually uses this new mode, debugging and crash
    recovery should become easier. This is because even when currently in
    the VT of a frozen X server it would still be possible to switch out
    by doing SysRq-r and then CTRL-, sshing in and
    doing chvt , or any other method of VT switching.
    The general concensus on #xorg-devel seems to be that it should be
    safe to use this with X now that we have KMS.

    This also moves the VT_ACKACQ define to a more appropriate place,
    for clarity's sake.

    Signed-off-by: Ari Entlich
    Acked-by: Alan Cox
    Signed-off-by: Greg Kroah-Hartman

    Ari Entlich
     

18 Dec, 2009

1 commit

  • Fix following warning in linux-next by guarding the function definition
    (both the "extern" and the inline) with #ifdef __KERNEL__.

    usr/include/linux/vt.h:89: userspace cannot call function or variable defined in
    the kernel

    Introduced by commit 5ada918b82399eef3afd6a71e3637697d6bd719f ("vt:
    introduce and use vt_kmsg_redirect() function").

    Signed-off-by: Bernhard Walle
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernhard Walle
     

16 Dec, 2009

1 commit

  • The kernel offers with TIOCL_GETKMSGREDIRECT ioctl() the possibility to
    redirect the kernel messages to a specific console.

    However, since it's not possible to switch to the kernel message console
    after a panic(), it would be nice if the kernel would print the panic
    message on the current console.

    This patch series adds a new interface to access the global kmsg_redirect
    variable by a function to be able to use it in code where
    CONFIG_VT_CONSOLE is not set (kernel/panic.c).

    This patch:

    Instead of using and exporting a global value kmsg_redirect, introduce a
    function vt_kmsg_redirect() that both can set and return the console where
    messages are printed.

    Change all users of kmsg_redirect (the VT code itself and kernel/power.c)
    to the new interface.

    The main advantage is that vt_kmsg_redirect() can also be used when
    CONFIG_VT_CONSOLE is not set.

    Signed-off-by: Bernhard Walle
    Cc: Alan Cox
    Cc: Ingo Molnar
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernhard Walle
     

20 Nov, 2009

1 commit

  • As this struct is exposed to user space and the API was added for this
    release it's a bit of a pain for the C++ world and we still have time to
    fix it. Rename the fields before we end up with that pain in an actual
    release.

    Signed-off-by: Alan Cox
    Reported-by: Olivier Goffart
    Signed-off-by: Linus Torvalds

    Alan Cox
     

20 Sep, 2009

3 commits

  • X and other graphical interfaces need to be able to flip to a console
    and lock it into graphics mode without races.

    Signed-off-by: Alan Cox
    Signed-off-by: Greg Kroah-Hartman

    Alan Cox
     
  • We have vt_kern.h for this

    Signed-off-by: Alan Cox
    Signed-off-by: Greg Kroah-Hartman

    Alan Cox
     
  • This is needed and requested in various forms for ConsoleKit, screenblank
    handling and the like so do the job with a single interface. Also build the
    interface so that unlike VT_WAITACTIVE and friends it won't miss events.

    FIXME: Should this be a waitactive ioctl or a new device file you can poll
    and read events from. We need the code anyway to fix up the existing broken
    wait for console switch logic but the ConsoleKit people would prefer the
    new device to the ioctl we have here

    Signed-off-by: Alan Cox
    Signed-off-by: Greg Kroah-Hartman

    Alan Cox
     

20 Oct, 2007

1 commit

  • Some external modules like Speakup need to monitor console output.

    This adds a VT notifier that such modules can use to get console output events:
    allocation, deallocation, writes, other updates (cursor position, switch, etc.)

    [akpm@linux-foundation.org: fix headers_check]
    Signed-off-by: Samuel Thibault
    Cc: Dmitry Torokhov
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Samuel Thibault
     

28 Aug, 2006

1 commit

  • When reading /dev/vcsa while a font with more than 256 characters is
    loaded, one of the attribute bits records the 9th bit of the character.
    But depending on the console driver (vgacon or fbcon for instance), that's
    bit 3 or bit 0. And there is no way for userland to know that, thus no way
    for userland to safely grab the screen content. So here is a (tested)
    patch:

    Add a VT_GETHIFONTMASK ioctl for knowing which bit is the 9th bit for VC
    text (vc_hi_font_mask field of the vc_data structure).

    Signed-off-by: Samuel Thibault
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Samuel Thibault
     

11 Jul, 2006

1 commit

  • MAX_NR_CONSOLES, fg_console, want_console and last_console are more of a
    function of the VT layer than the TTY one. Moving these to vt.h and vt_kern.h
    allows all of the framebuffer and VT console drivers to remove their
    dependency on tty.h.

    [akpm@osdl.org: fix alpha build]
    Signed-off-by: Jon Smirl
    Signed-off-by: Antonino Daplas
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jon Smirl
     

17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds