From: Alessandro Rubini <rubini@gnudd•com>
To: linuxppc-embedded@ozlabs•org
Subject: Re: login on console=tty with serial input
Date: Fri, 16 Mar 2007 23:42:45 +0100 [thread overview]
Message-ID: <20070316224245.GA32224@mail.gnudd.com> (raw)
In-Reply-To: <381D3B2C62C8B94B95219E2DA47C8DCF08E3CA@stnzolex2.securiton.int>
> As GUI library, I started to evaluate Nano-X, FLTK and wxWitgets. But there
> is the problem that I don't have keyboard input whether form the serial
> line nor form a remote shell (Ethernet).
What you type in the serial console reaches user space in /dev/ttyS0
or whatever the name on your platform. What you type in the network
connection reaches user space in the socket, where the server (sshd,
telnetd or whatever) pushes it back to a pty master, so your shell
reads it from the pty (slave) is has on its stdin.
Programs using /dev/fb usually open /dev/tty1 (or /dev/tty2 etc) to
read keyboard input from. The device driver that manages it is nether
the serial driver nor the pty driver, but the "virtual console" one.
What is reported there as keypresses are the input events reported by
a keyboard.
> As far I understand the matter the problem is that the console that is
> running on the frame buffer needs as input a keyboard device and not a
> serial line. Unfortunately I found till now no solution to redirect the
> serial line to a keyboard device.
Read /dev/ttyS0 and post keypress events associated to the ascii data
you read. Your graphic environment will see them. You can write
your own module to post keyboard data or use uinput (CONFIG_INPUT_UINPUT).
hope this helps
/alessandro
prev parent reply other threads:[~2007-03-16 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:21 login on console=tty with serial input hbruegge
2007-03-16 13:39 ` Daniel.Wyss
2007-03-16 22:42 ` Alessandro Rubini [this message]
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=20070316224245.GA32224@mail.gnudd.com \
--to=rubini@gnudd$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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