This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: STOUT redirection (was Re: Newbie question)
- To: Jonathan Larmour <jlarmour at redhat dot com>,Ecos-Discuss <ecos-discuss at sourceware dot cygnus dot com>
- Subject: Re: [ECOS] STOUT redirection (was Re: [ECOS] Newbie question)
- From: Carlos Sobrinho <epilog at netvisao dot pt>
- Date: Mon, 02 Jul 2001 22:38:38 +0100
- References: <4.3.2.7.2.20010627231904.00b422d8@mail.larwe.com> <003101c0ffb7$144db970$de0110ac@DELLPH> <3B4036CE.9080306@netvisao.pt> <3B40E8D2.BCC94FAC@redhat.com>
Jonathan Larmour wrote:
> Carlos Sobrinho wrote:
>
>> Hi there. I know this is an old question but here goes.
>> I want to put a graphical display in my AEB-1 board and a PS2 keyboard
>> (that's not the main problem) but I want to send a copy of the info
>> passed to the stdout and stderr to the display, like GDB packets and
>> System errors from stderr and some redirection of the keyboard data to
>> the buffer of the serial port.Just a "simple" copy and not a "move".The
>> serial port should receive the info always to permit debugging.
>
>
> You _could_ just call your appropriate screen output function in the serial
> output functions in hal/arm/aeb/VERSION/src/hal_diag.c. But input is more
> difficult. It would be much easier if you could create a new channel
> (especially a "virtual vector" channel as used in current CVS sources)
"virtual vector" ? any info about that? Maybe a little example?
Thanks in advance
> instead.
>
> Jifl