This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Help: How to get Keyboard input in synthetic environmet?
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Zhangzheng <zzhang at acornsoftcorp dot com>
- Cc: Andrew Lunn <andrew dot lunn at ascom dot ch>,eCos_discuss <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 20 Mar 2003 12:12:56 +0000
- Subject: Re: [ECOS] Help: How to get Keyboard input in synthetic environmet?
- References: <200303200350399.SM00183@Longbow>
Zhangzheng wrote:
> Hi:
>
> Thanks for your answers!
> I have tried this way, and my application can read characters from stdin
> in Linux terminal not in the synthetic console. And it doesn't like a normal
> CLI cause the input and output is seperated in two consoles.
> As there are no interrupt associated with the stdin, it seems that other
> threads in my application will be blocked by the waiting of stdin.
> If I asign a much lower priority to the CLI session, do the other threads
> can work properly?
Nope, if you need that, you should follow what Andrew suggested and write
a fake serial driver. We don't yet have a proper keyboard device driver
system in eCos, and if we did it would probably be linked in with other
user-interface things (think Microwindows).
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss