summaryrefslogtreecommitdiffstats
path: root/sys/dev/syscons
Commit message (Collapse)AuthorAgeFilesLines
* Rename a variable to match scvidctl.c.jkim2010-11-301-11/+11
|
* Stop hardcoding default font size.jkim2010-11-301-1/+1
|
* Clean up code a bit to make it more readable.jkim2010-11-301-42/+40
|
* Clean up code a bit to make it more readable.jkim2010-11-291-18/+9
|
* Honor font size for the video mode when default fonts are compiled in kerneljkim2010-11-291-9/+35
| | | | and VESA mode is enabled from loader.
* Fix typos.brucec2010-11-091-3/+3
| | | | | PR: bin/148894 Submitted by: olgeni
* Explicitly tell the compiler that we don't care about the return valuerpaulo2010-10-131-11/+11
| | | | of kbdd_ioctl().
* Rework r210248. Although it fixed most of problems, it did not fix onejkim2010-09-171-7/+4
| | | | | | | | | particular edge case where X-axis resolution is not multiple of font width. Now we just advance enough scan lines, then deduct a partial scan line. It is more intuitive than the previous code. Apply the same wisdom to EGA and VGA planar renderers for consistency. Reported by: David DEMELIER (demelier dot david at gmail dot com)
* Improve style slightly.jkim2010-07-191-47/+50
|
* Fix two long-standing line wrapping bugs in VGA renderer for pixel mode.jkim2010-07-191-2/+3
| | | | | | | Font size may be smaller than 16 and logical scan line may be larger than the displayed scan line. MFC after: 3 days
* Suspend screen updates when the video controller is powered down.jkim2010-05-222-2/+3
|
* Correct beastie_saver module name.jkim2010-04-071-0/+4
|
* Add the official FreeBSD logo image file for logo_saver.jkim2010-04-071-350/+833
|
* Copy Beastie image file to prepare for an official logo image.jkim2010-04-071-0/+358
|
* Refine r204265. We want the standard VGA palette for packed pixel mode.jkim2010-03-292-4/+4
|
* Align memory access of 24-bit pixel renderer to word boundary.jkim2010-03-241-2/+7
|
* Separate 24-bit pixel draw from 32-bit case. Although it is slower, we dojkim2010-03-231-1/+4
| | | | not want to write a useless zero to inaccessible memory region.
* Improve VESA mode switching via loader tunable `hint.sc.0.vesa_mode'.jkim2010-02-243-64/+123
| | | | The most notable change is history buffer is fully saved/restored now.
* Yet another attempt to make palette loading more safer:jkim2010-02-233-6/+29
| | | | | | | | | - 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.
* The New and Improved snake_server - Service Pack 1: now even moreivoras2010-02-231-1/+1
| | | | sensitive to load average variations!
* Upgrade the "snake" syscons screensaver to the new, multimedia version!ivoras2010-02-231-6/+49
| | | | | | Now, with color! And system load averages! Amused by it: gnn
* Update d_mmap() to accept vm_ooffset_t and vm_memattr_t.rnoland2009-12-291-2/+3
| | | | | | | | | | | | | This replaces d_mmap() with the d_mmap2() implementation and also changes the type of offset to vm_ooffset_t. Purge d_mmap2(). All driver modules will need to be rebuilt since D_VERSION is also bumped. Reviewed by: jhb@ MFC after: Not in this lifetime...
* Include <sys/ttydefaults.h>, instead of doing it through <sys/termios.h>.ed2009-11-281-0/+1
| | | | I want to prevent the header polution of <sys/termios.h> eventually.
* Fix pgsignal() call after signature change in r199355.kib2009-11-171-1/+5
| | | | | Reported and tested by: bf1783 googlemail com MFC after: 1 month
* Convert syscons on i386 to TERM=xterm.ed2009-11-131-9/+0
| | | | | TEKEN_XTERM is now gone. Because we always use xterm mode now, we only need a TEKEN_CONS25 switch to go back to cons25.
* Switch the default terminal emulation style to xterm for most platforms.ed2009-11-131-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now syscons(4) uses a cons25-style terminal emulator. The disadvantages of that are: - Little compatibility with embedded devices with serial interfaces. - Bad bandwidth efficiency, mainly because of the lack of scrolling regions. - A very hard transition path to support for modern character sets like UTF-8. Our terminal emulation library, libteken, has been supporting xterm-style terminal emulation for months, so flip the switch and make everyone use an xterm-style console driver. I still have to enable this on i386. Right now pc98 and i386 share the same /etc/ttys file. I'm not going to switch pc98, because it uses its own Kanji-capable cons25 emulator. IMPORTANT: What to do if things go wrong (i.e. graphical artifacts): - Run the application inside script(1), try to reduce the problem and send me the log file. - In the mean time, you can run `vidcontrol -T cons25' and `export TERM=cons25' so you can run applications the same way you did before. You can also build your kernel with `options TEKEN_CONS25' to make all virtual terminals use the cons25 emulator by default. Discussed on: current@
* Allow Syscons terminal emulators to provide function key strings.ed2009-11-113-13/+78
| | | | | | | | | 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.
* Fix VESA color palette corruption:jkim2009-11-031-0/+3
| | | | | | | | | | | | - VBE 3.0 says palette format resets to 6-bit mode when video mode changes. We simply set 8-bit mode when we switch modes if the adapter supports it. - VBE 3.0 also says if the mode is not VGA compatible, we must use VBE function to save/restore palette. Otherwise, VGA function may be used. Thus, reinstate the save/load palette functions only for non-VGA compatible modes regardless of its palette format. - Let vesa(4) set VESA modes even if vga(4) claims to support it. - Reset default palette if VESA pixel mode is set initially. - Fix more style nits.
* Search for default 800x600 graphics mode from supported VESA mode list.jkim2009-10-231-18/+46
| | | | Many video controllers do not support 800x600x24 mode any more.
* Add support for VT200-style mouse input.ed2009-09-274-9/+65
| | | | | | | | | | | | | | | | | | | 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 <onemda gmail com> Tested with: vim(1)
* Add 256 color support.ed2009-09-261-4/+4
| | | | | | | | | | | | | | It is quite inconvenient that if an application for xterm uses 256 color mode, text suddenly starts to blink (because of ;5; in the middle). We'd better just implement 256 color mode and add a conversion routine from 256 to 8 color mode, which doesn't seem to be too bad in practice. Remapping colors is done quite simple. If one of the channels is most actively represented, primary colors are used. If two channels are most actively represented, secondary colors are used. If all three channels are equal (gray), it picks between black and white. Reported by: Paul B. Mahol <onemda gmail com>
* Just use ttydisc_rint_simple() instead of doing it ourselves.ed2009-09-181-8/+2
| | | | | | | This code seems to do exactly the same as ttydisc_rint_simple() does nowadays. Just remove it. Obtained from: //depot/user/ed/newcons/sys/dev/syscons/syscons.c
* Make sure we never place the cursor outside the screen.ed2009-09-131-3/+6
| | | | | | | | | | For some vague reason, it may be possible that scp->cursor_pos exceeds scp->ysize * scp->xsize. This means that teken_set_cursor() may get called with an invalid position. Just ignore the old cursor position in this case. Reported by: Paul B. Mahol <onemda gmail com> MFC after: 1 month
* Commit a change that I missed in the previous commit.ed2009-09-121-0/+4
| | | | I ran `svn commit' in sys/teken/, instead of sys/.
* Make 8-bit support run-time configurable.ed2009-09-121-0/+3
| | | | | Now to do the same for xterm support. This means people can eventually toy around with xterm+UTF-8 without recompiling their kernel.
* Make use of the more flexable device hints by adding a new field,delphij2009-09-121-2/+3
| | | | vesa_mode to specify VESA mode, as suggested by jhb@.
* Extend the usage of sc(4)'s hint variable 'flag'. Bit 0x80 now meansdelphij2009-09-112-8/+15
| | | | | | | | | | "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 <ddkprog yahoo com>, swell k at gmail.com with some minor changes.
* Don't malloc a buffer while holding the prison0 mutex. Instead, use a loopjhb2009-09-101-3/+15
| | | | | | | | | where we figure out the hostname length under the lock, malloc the buffer with the lock dropped, then recheck the length under the lock and loop again if the buffer is now too small. Tested by: Norbert Koch nkoch demig de MFC after: 3 days
* - Teach vesa(4) and dpms(4) about x86emu. [1]delphij2009-09-091-1/+1
| | | | | | | | | | - Add vesa kernel options for amd64. - Connect libvgl library and splash kernel modules to amd64 build. - Connect manual page dpms(4) to amd64 build. - Remove old vesa/dpms files. Submitted by: paradox <ddkprog yahoo com> [1], swell k at gmail.com (with some minor tweaks)
* Expose the TF_REVERSE flag to the console driver.ed2009-09-031-3/+11
| | | | | | | | | | | | | | | Right now libteken processes TF_REVERSE internally and returns the toggled colors to the console driver. This isn't entirely correct. This means that the bold flag is always processed by the foreground color, while reversing should be done after the foreground color has been set to a brighter version by the bold flag. This is no problem with the syscons driver, because with VGA it only supports 16 foreground and 8 background colors. My WIP console driver reconfigures the graphics hardware to disable the blink functionality and uses 16 foreground and 16 background colors. This means that this driver will handle the TF_REVERSE flag a little different from what syscons does right now.
* Move libteken out of the syscons directory.ed2009-09-0312-2898/+1
| | | | | | | | | | I initially committed libteken to sys/dev/syscons/teken, but now that I'm working on a console driver myself, I noticed this was not a good decision. Move it to sys/teken to make it easier for other drivers to use a terminal emulator. Also list teken.c in sys/conf/files, instead of listing it in all the files.arch files separately.
* Fix VESA modes and allow 8bit depth modes.delphij2009-08-242-1/+23
| | | | | | PR: i386/124902 Submitted by: paradox <ddkprog yahoo com> MFC after: 2 months
* Small fixes to Unicode handling:ed2009-06-162-38/+43
| | | | | - Add more mappings for Greek characters and the Euro sign. - Print UTF-8 characters in the log file as hexadecimal.
* Add more entries to the Unicode-to-CP437 table.ed2009-06-141-9/+15
| | | | | | | | | Characters between 0x07 and 0x0d are now also mapped, which means we can display almost 256 different characters. Also remap certain types of dashes and quotes, which means we can finally read our manual pages without red question marks in them. Submitted by: Christoph Mallon
* Rename the host-related prison fields to be the same as the host.*jamie2009-06-131-2/+2
| | | | | | | parameters they represent, and the variables they replaced, instead of abbreviated versions of them. Approved by: bz (mentor)
* Make the proof-of-concept UTF-8 support in Syscons less useless.ed2009-06-131-18/+121
| | | | | | | | | | Add a small Unicode-to-CP437 remapping table to at least demonstrate that the terminal emulator is perfectly capable of handling UTF-8. This will of course break if the user loads a different font map, but it at least allows people to give it a try. I can now see the box drawing in dialog(1) and the arrows in mutt(1) correctly.
* Make the demo/stress tools build again, after my changes to param().ed2009-06-102-2/+2
|
* Restore support for bell pitch/duration.ed2009-05-315-3/+20
| | | | | | | | Because we only support a single argument to tf_param, use 16 bits for the pitch and 16 bits for the duration. While there, make the argument unsigned. There isn't a single param call that needs a signed integer. Submitted by: danfe (modified)
* Place hostnames and similar information fully under the prison system.jamie2009-05-291-4/+5
| | | | | | | | | | | | | | | | | The system hostname is now stored in prison0, and the global variable "hostname" has been removed, as has the hostname_mtx mutex. Jails may have their own host information, or they may inherit it from the parent/system. The proper way to read the hostname is via getcredhostname(), which will copy either the hostname associated with the passed cred, or the system hostname if you pass NULL. The system hostname can still be accessed directly (and without locking) at prison0.pr_host, but that should be avoided where possible. The "similar information" referred to is domainname, hostid, and hostuuid, which have also become prison parameters and had their associated global variables removed. Approved by: bz (mentor)
* Last minute TTY API change: remove mutex argument from tty_alloc().ed2009-05-292-2/+2
| | | | | | | | | | I don't want people to override the mutex when allocating a TTY. It has to be there, to keep drivers like syscons happy. So I'm creating a tty_alloc_mutex() which can be used in those cases. tty_alloc_mutex() should eventually be removed. The advantage of this approach, is that we can just remove a function, without breaking the regular API in the future.
OpenPOWER on IntegriCloud