Attachment 99168 Details for Bug 78796 – patch suggestion

patch suggestion

systemd-vconsole.diff (text/plain), 1.55 KB, created by Carl Schaefer on 2014-05-16 19:16:23 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Carl Schaefer

Created: 2014-05-16 19:16:23 UTC

Size: 1.55 KB

patch

obsolete

>--- vconsole-setup.c~	2013-08-13 16:02:47.237713642 -0400
>+++ vconsole-setup.c	2014-02-28 00:43:07.067877227 -0500
>@@ -181,6 +181,10 @@
> static void font_copy_to_all_vcs(int fd) {
>         struct vt_stat vcs = {};
>         int i, r;
>+        unsigned char map8[E_TABSZ];
>+        unsigned short map16[E_TABSZ];
>+        struct unimapdesc unimapd;
>+        struct unipair unipairs[USHRT_MAX];
> 
>         /* get active, and 16 bit mask of used VT numbers */
>         r = ioctl(fd, VT_GETSTATE, &vcs);
>@@ -209,6 +213,26 @@
>                 cfo.op = KD_FONT_OP_COPY;
>                 cfo.height = vcs.v_active-1; /* tty1 == index 0 */
>                 ioctl(vcfd, KDFONTOP, &cfo);
>+
>+                /* copy map of 8bit chars */
>+                if (ioctl(  fd, GIO_SCRNMAP, map8) == 0)
>+                    ioctl(vcfd, PIO_SCRNMAP, map8);
>+
>+                /* copy map of 8bit chars -> 16bit Unicode values */
>+                if (ioctl(  fd, GIO_UNISCRNMAP, map16) == 0)
>+                    ioctl(vcfd, PIO_UNISCRNMAP, map16);
>+
>+                /* copy unicode translation table */
>+                /* unimapd is a ushort count and a pointer to an
>+                   array of struct unipair { ushort, ushort } */
>+                unimapd.entries  = unipairs;
>+                unimapd.entry_ct = USHRT_MAX;
>+                if (ioctl(fd, GIO_UNIMAP, &unimapd) == 0) {
>+                        struct unimapinit adv = { 0, 0, 0 };
>+
>+                        ioctl(vcfd, PIO_UNIMAPCLR, &adv);
>+                        ioctl(vcfd, PIO_UNIMAP, &unimapd);
>+                }
>         }
> }
>

Actions: View

Attachments on bug 78796: 99168

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.