From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: [kbd] [ANNOUNCE] kbd-2.6-rc1
Date: Mon, 8 May 2023 15:48:55 +0200 [thread overview]
Message-ID: <ZFj9x+4/i9MgvG4W@example.org> (raw)
kbd 2.6-rc1 Release Notes
-------------------------
The kbd-2.6-rc1 is available at
https://mirrors.edge.kernel.org/pub/linux/utils/kbd/kbd-2.6-rc1.tar.gz
https://mirrors.edge.kernel.org/pub/linux/utils/kbd/kbd-2.6-rc1.tar.xz
https://mirrors.edge.kernel.org/pub/linux/utils/kbd/kbd-2.6-rc1.tar.sign
Changes
-------
libkfont:
* Leverage KD_FONT_OP_GET/SET_TALL font operations. The new
KD_FONT_OP_GET/SET_TALL font operations allow to load fonts taller
than 32 pixels by dropping the VGA-specific vertical pitch limitation
(requires kernel 6.2 or later).
* Use threadsafe strtok_r.
* Increase soname version.
setvtrgb:
* Fix read from pipe. The pipe is not rewindable, but we don't really
need to rewind() but we need to unread one character.
keymaps:
* i386/dvorak/dvorak-de.map: Add dvorak-de.map from console-data.
* i386/qwerty/is-latin1.map: the circumflex should also be available in
its original level-3 position.
* i386/qwerty/la-latin1.map: Convert the characters expressed in Latin-1
to the named constants, to ease up transition to Unicode.
* pine/en.map: New version of pinephone keyboard map file.
unimaps:
* Add mapping for U+25CF. The unicode maps in font files like
eurlatgr.psfu and cp850-8x16.psfu have an entry for U+25CF, but the
plaintext unimap files do not.
tests:
* Use strace to track syscalls. Now strace is powerful enough to show
ioctls specific to console configuration.
Git repository
--------------
git://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git
Feedback and bug reports, as always, are welcomed.
--
Rgrds, legion
reply other threads:[~2023-05-08 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZFj9x+4/i9MgvG4W@example.org \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).