All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Daniel Vetter <daniel@ffwll.ch>,
	Martin Hostettler <textshell@uchuujin.de>,
	Peilin Ye <yepeilin.cs@gmail.com>,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] VT_RESIZEX fixes
Date: Thu, 13 May 2021 02:37:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2105090548170.2587@angie.orcam.me.uk> (raw)

Hi,

 I got to the bottom of the issue with VT_RESIZEX recently discussed and 
came up with this small patch series, fixing an additional issue that I 
originally thought might be broken VGA hardware emulation with my laptop, 
which however turned out to be intertwined with the original problem and 
also a regression introduced somewhat later.  This had to become 1/3 then 
and to make backporting feasible I had to put a revert of the offending 
change from last Sep next, followed by a proper fix for the framebuffer 
issue the Sep change tried to address.

 See individual change descriptions for details.

 These have been verified with true VGA hardware (a Trident TVGA8900 ISA 
video adapter) using various combinations of `svgatextmode' and `setfont' 
command invocations to change both the VT size and the font size, and also 
switching between the text console and X11, both by starting/stopping the 
X server and by switching between VTs.  All this to ensure bringing the 
behaviour of VGA text console back to correct operation as it used to be 
with Linux 2.6.18.

 A minor glitch observed was that when I called `svgatextmode' while 
running X11 the screen became garbled and upon a subsequent VT switch to a 
text console the machine locked up hard right away.  This might require 
further attention, but is not itself a problem with this patch series or a 
regression.

 Please apply then.

  Maciej

WARNING: multiple messages have this Message-ID (diff)
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Jiri Slaby <jirislaby@kernel.org>
Cc: linux-fbdev@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Martin Hostettler <textshell@uchuujin.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peilin Ye <yepeilin.cs@gmail.com>
Subject: [PATCH 0/3] VT_RESIZEX fixes
Date: Thu, 13 May 2021 02:37:13 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2105090548170.2587@angie.orcam.me.uk> (raw)

Hi,

 I got to the bottom of the issue with VT_RESIZEX recently discussed and 
came up with this small patch series, fixing an additional issue that I 
originally thought might be broken VGA hardware emulation with my laptop, 
which however turned out to be intertwined with the original problem and 
also a regression introduced somewhat later.  This had to become 1/3 then 
and to make backporting feasible I had to put a revert of the offending 
change from last Sep next, followed by a proper fix for the framebuffer 
issue the Sep change tried to address.

 See individual change descriptions for details.

 These have been verified with true VGA hardware (a Trident TVGA8900 ISA 
video adapter) using various combinations of `svgatextmode' and `setfont' 
command invocations to change both the VT size and the font size, and also 
switching between the text console and X11, both by starting/stopping the 
X server and by switching between VTs.  All this to ensure bringing the 
behaviour of VGA text console back to correct operation as it used to be 
with Linux 2.6.18.

 A minor glitch observed was that when I called `svgatextmode' while 
running X11 the screen became garbled and upon a subsequent VT switch to a 
text console the machine locked up hard right away.  This might require 
further attention, but is not itself a problem with this patch series or a 
regression.

 Please apply then.

  Maciej

             reply	other threads:[~2021-05-13  0:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  0:37 Maciej W. Rozycki [this message]
2021-05-13  0:37 ` [PATCH 0/3] VT_RESIZEX fixes Maciej W. Rozycki
2021-05-13  0:37 ` [PATCH 1/3] vgacon: Record video mode changes with VT_RESIZEX Maciej W. Rozycki
2021-05-13  0:37   ` Maciej W. Rozycki
2021-05-13  0:37 ` [PATCH 2/3] vt_ioctl: Revert VT_RESIZEX parameter handling removal Maciej W. Rozycki
2021-05-13  0:37   ` Maciej W. Rozycki
2021-05-13  0:37 ` [PATCH 3/3] vt: Fix character height handling with VT_RESIZEX Maciej W. Rozycki
2021-05-13  0:37   ` Maciej W. Rozycki

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=alpine.DEB.2.21.2105090548170.2587@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=textshell@uchuujin.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yepeilin.cs@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.