Hi all
I am using the kernel (2.6.15) in an ppc-based embedded system through a
serial console on ttyS0 with no problems.
Now I attached a graphic card to the system, which is correctly
recognized and initialised by the Kernel. If I add "console=tty0
console=ttyS0,57600" to the bootargs, I have the boot messages of the
kernel on the screen and a login on the ttyS0.
What I now want to do is to disable the serial console and use the
graphic card as output and the raw character data (ASCII) coming in from
the terminal connected to the rs232 as input.
I have a login on the screen, if I delete the line console=ttyS0,57600
from the bootargs, but unfortunately no input if a key is pressed on the
terminal keyboard.
So my problem and question is, apart from not totally understanding the
input device system of 2.6.x ;-)
Has anyone ever done that?
Is it just a kernel configuration problem? If so what modules have to be
compiled in?
Are there any good documentaion about the new input device system ?
Basically I am totally confused ;-), so any ideas are appreciated.
Cheers
Harald
On Tue, 6 Jun 2006 hbruegge@rockwellcollins.com wrote:
Hi all
I am using the kernel (2.6.15) in an ppc-based embedded system through a
serial console on ttyS0 with no problems.
Now I attached a graphic card to the system, which is correctly
recognized and initialised by the Kernel. If I add "console=tty0
console=ttyS0,57600" to the bootargs, I have the boot messages of the
kernel on the screen and a login on the ttyS0.
What I now want to do is to disable the serial console and use the
graphic card as output and the raw character data (ASCII) coming in from
the terminal connected to the rs232 as input.
Well, it is possible... The keyword to google for is inputattach. A
hint - it is a part of the linux-console package on sourceforge:
http://linuxconsole.cvs.sourceforge.net/linuxconsole/ruby/utils/. You
probably will have to write some glue driver. Or, probably, an easier
option - write a user-space daemon that reads from /dev/ttyS0 and sends
events to uinput. With this you don't need any kernel drivers - just a
user-space daemon.
HTH
Guennadi
---
Guennadi Liakhovetski
quoted
quoted
quoted
quoted
"Guennadi" == Guennadi Liakhovetski [off-list ref] writes:
Hi,
Guennadi> Or, probably, an easier option - write a user-space daemon
Guennadi> that reads from /dev/ttyS0 and sends events to uinput. With
Guennadi> this you don't need any kernel drivers - just a user-space
Guennadi> daemon.
handhelds.org's kbdd is such a daemon. See
http://handhelds.org/cgi-bin/cvsweb.cgi/apps/kbdd/
--
Bye, Peter Korsgaard