src/sys/dev/syscons/syscons.h, branch stable/9

MFC r228644: syscons: provide a first iteration of cngrab/cnungrab

2012-05-13T17:11:49Z

implementation

MFC r228426: syscons: make sc_puts static as it is used only privately

2012-01-15T22:04:28Z

Add support for alternative break-to-debugger to syscons(4). While most

2011-08-27T22:10:45Z

keyboards allow console break sequences (such as ctrl-alt-esc) to be entered, alternative break can prove useful under virtualisation and remote console systems where entering control sequences can be difficult or unreliable. MFC after: 3 weeks Approved by: re (bz)

Move VT switching hack for suspend/resume from bus drivers to syscons.c

2011-05-09T18:46:49Z

using event handlers. A different version was Submitted by: Taku YAMAMOTO (taku at tackymt dot homeip dot net)

Suspend screen updates when the video controller is powered down.

2010-05-22T07:35:17Z

Improve VESA mode switching via loader tunable `hint.sc.0.vesa_mode'.

2010-02-24T20:13:34Z

The most notable change is history buffer is fully saved/restored now.

Yet another attempt to make palette loading more safer:

2010-02-23T21:51:14Z

- Add a separate palette data for 8-bit DAC mode when SC_PIXEL_MODE is set and fill it up with default gray-scale palette data for text. Now we don't have to set `hint.sc.0.vesa_mode' to get the default palette data. - Add a new adapter flag, V_ADP_DAC8 to track whether the controller is using 8-bit palette format and load correct palette when switching modes. - Set 8-bit DAC mode only for non-VGA compatible graphics mode.

Allow Syscons terminal emulators to provide function key strings.

2009-11-11T08:20:19Z

xterm and cons25 have some incompatibilities when it comes to escape sequences for special keys, such as F1 to F12, home, end, etc. Add a new te_fkeystr() that can be used to override the strings. scterm-sck won't do anything with this, but scterm-teken will use teken_get_sequences() to obtain the proper sequence.

Add support for VT200-style mouse input.

2009-09-27T18:19:41Z

Right now if applications want to use the mouse on the command line, they use sysmouse(4) and install a signal handler in the kernel to deliver signals when mouse events arrive. This conflicts with my plan to change to TERM=xterm, so implement proper VT200-style mouse input. Because mouse input is now streamed through the TTY, it means you can now SSH to another system on the console and use the mouse there as well. The disadvantage of the VT200 mouse protocol, is that it doesn't seem to generate events when moving the cursor. Only when pressing and releasing mouse buttons. There are different protocols as well, but this one seems to be most commonly supported. Reported by: Paul B. Mahol Tested with: vim(1)

Extend the usage of sc(4)'s hint variable 'flag'. Bit 0x80 now means

2009-09-11T02:07:24Z

"set vesa mode" and higher 16bits of the flag would be the desired mode. One can now set, for instance, hint.sc.0.flags=0x01680180, which means that the system should set VESA mode 0x168 upon boot. Submitted by: paradox , swell k at gmail.com with some minor changes.