From: David Lechner <david@lechnology.com>
To: linux-fbdev@vger.kernel.org
Cc: David Lechner <david@lechnology.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Invert margin colors when terminal is inverted
Date: Mon, 31 Jul 2017 19:09:43 +0000 [thread overview]
Message-ID: <1501528185-9976-1-git-send-email-david@lechnology.com> (raw)
This is v2 of "fbcon: Use background color for margins​"[1].
It turns out that using the text background color was not a good choice. So,
I've started over.
In this series, the margin color depends on the terminal's inversion state. If
it is not inverted, then the margins are black as they currently are. But now,
if the terminal is inverted, the margin color is also inverted, so it is white.
In order to detect when the terminal is inverted, I had to add a notifier
callback for the VT_UPDATE event. Otherwise, running `setterm -inverse on`
would not change the margins until I also ran `clear`.
[1]: https://patchwork.kernel.org/patch/9869421/
David Lechner (2):
fbcon: Invert margin colors when terminal is inverted
fbcon: add VT notifier for VT_UPDATE event
drivers/video/console/bitblit.c | 2 +-
drivers/video/console/fbcon.c | 28 ++++++++++++++++++++++++++++
drivers/video/console/fbcon_ccw.c | 2 +-
drivers/video/console/fbcon_cw.c | 2 +-
drivers/video/console/fbcon_ud.c | 2 +-
5 files changed, 32 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2017-07-31 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 19:09 David Lechner [this message]
2017-07-31 19:09 ` [PATCH v2 1/2] fbcon: Invert margin colors when terminal is inverted David Lechner
2017-07-31 19:09 ` [PATCH v2 2/2] fbcon: add VT notifier for VT_UPDATE event David Lechner
2017-07-31 19:30 ` [PATCH v2 0/2] Invert margin colors when terminal is inverted Alan Cox
2017-07-31 20:43 ` David Lechner
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=1501528185-9976-1-git-send-email-david@lechnology.com \
--to=david@lechnology.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).