From: thierry.moreau@connotech.com (Thierry Moreau)
To: linus-amlogic@lists.infradead.org
Subject: Suggestion for better HDMI console support
Date: Wed, 16 May 2018 19:47:53 +0000 [thread overview]
Message-ID: <5AFC8AE9.1000104@connotech.com> (raw)
Dear kernel developers,
I experimented with Odroid C2 Linux installation and I wanted an HDMI
display console. I succeeded but I needed a workaround which I report below.
My suggestion today is to implement the workaround logic inside the
kernel, which should be (technically at least) easy for some of you.
I noticed that the serial console is often suggested as a highly
recommended alternative for Amlogic SOC development. Maybe my suggestion
would change this (making the HDMI console working out of the box).
The problem I experienced with the Odroid C2 hdmi console display
output: for unknown reason, the kernel initializes the hdmi output in a
blank screen state that is exited only if the kernel receives two
requests: first to blank the (already blanked) screen and then to
unblank the screen. This sequence happens if a connected keyboard is
idle for 15 minutes and then touched by the user.
The workaround: I wrote a small C program that makes the two kernel
requests without wait.
Here is a snapshot:
#include <sys/ioctl.h>
#include <linux/vt.h>
#include <linux/tiocl.h>
static int blank_code=TIOCL_BLANKSCREEN;
static int unblank_code=TIOCL_UNBLANKSCREEN;
int main(int argc, char *argv[])
{
int td;
td=open("/dev/tty0",O_RDWR|O_NOCTTY);
if (td>=0) {
ioctl(td,TIOCLINUX,&blank_code);
ioctl(td,TIOCLINUX,&unblank_code);
}
}
My kernel version is 3.16.56 as customized to Odroid C2 by Hardkernel.
"Hope it helps!"
- Thierry Moreau
P.S. I am chasing installation hints for the Amlogic closed source
libraries for X.11 support in an otherwise plain vanilla Linux
innstallation (headless and server working fine). Any suggestion as
sources of info?
reply other threads:[~2018-05-16 19:47 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=5AFC8AE9.1000104@connotech.com \
--to=thierry.moreau@connotech.com \
--cc=linus-amlogic@lists.infradead.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