summaryrefslogtreecommitdiffstats
path: root/sys/conf/files.sparc64
diff options
context:
space:
mode:
authored <ed@FreeBSD.org>2009-01-01 13:26:53 +0000
committered <ed@FreeBSD.org>2009-01-01 13:26:53 +0000
commit0596e3449bae55cdc93922846db4c24ac0201bdd (patch)
tree800c6eb7ee8ad57502db7890e80360e20d29a5d8 /sys/conf/files.sparc64
parent6b469d082cfbaa8c5d6f0e4eaa3f3baff098104a (diff)
downloadFreeBSD-src-0596e3449bae55cdc93922846db4c24ac0201bdd.zip
FreeBSD-src-0596e3449bae55cdc93922846db4c24ac0201bdd.tar.gz
Replace syscons terminal renderer by a new renderer that uses libteken.
Some time ago I started working on a library called libteken, which is terminal emulator. It does not buffer any screen contents, but only keeps terminal state, such as cursor position, attributes, etc. It should implement all escape sequences that are implemented by the cons25 terminal emulator, but also a fair amount of sequences that are present in VT100 and xterm. A lot of random notes, which could be of interest to users/developers: - Even though I'm leaving the terminal type set to `cons25', users can do experiments with placing `xterm-color' in /etc/ttys. Because we only implement a subset of features of xterm, this may cause artifacts. We should consider extending libteken, because in my opinion xterm is the way to go. Some missing features: - Keypad application mode (DECKPAM) - Character sets (SCS) - libteken is filled with a fair amount of assertions, but unfortunately we cannot go into the debugger anymore if we fail them. I've done development of this library almost entirely in userspace. In sys/dev/syscons/teken there are two applications that can be helpful when debugging the code: - teken_demo: a terminal emulator that can be started from a regular xterm that emulates a terminal using libteken. This application can be very useful to debug any rendering issues. - teken_stress: a stress testing application that emulates random terminal output. libteken has literally survived multiple terabytes of random input. - libteken also includes support for UTF-8, but unfortunately our input layer and font renderer don't support this. If users want to experiment with UTF-8 support, they can enable `TEKEN_UTF8' in teken.h. If you recompile your kernel or the teken_demo application, you can hold some nice experiments. - I've left PC98 the way it is right now. The PC98 platform has a custom syscons renderer, which supports some form of localised input. Maybe we should port PC98 to libteken by the time syscons supports UTF-8? - I've removed the `dumb' terminal emulator. It has been broken for years. It hasn't survived the `struct proc' -> `struct thread' conversion. - To prevent confusion among people that want to hack on libteken: unlike syscons, the state machines that parse the escape sequences are machine generated. This means that if you want to add new escape sequences, you have to add an entry to the `sequences' file. This will cause new entries to be added to `teken_state.h'. - Any rendering artifacts that didn't occur prior to this commit are by accident. They should be reported to me, so I can fix them. Discussed on: current@, hackers@ Discussed with: philip (at 25C3)
Diffstat (limited to 'sys/conf/files.sparc64')
-rw-r--r--sys/conf/files.sparc643
1 files changed, 2 insertions, 1 deletions
diff --git a/sys/conf/files.sparc64 b/sys/conf/files.sparc64
index 311027c..90c37a9 100644
--- a/sys/conf/files.sparc64
+++ b/sys/conf/files.sparc64
@@ -55,8 +55,9 @@ dev/pcf/pcf_ebus.c optional pcf ebus
dev/sound/sbus/cs4231.c optional snd_audiocs ebus | \
snd_audiocs sbus
dev/syscons/scgfbrndr.c optional sc
-dev/syscons/scterm-sc.c optional sc
+dev/syscons/scterm-teken.c optional sc
dev/syscons/scvtb.c optional sc
+dev/syscons/teken/teken.c optional sc
dev/uart/uart_cpu_sparc64.c optional uart
dev/uart/uart_kbd_sun.c optional uart sc
kern/syscalls.c optional ktr
OpenPOWER on IntegriCloud