From: Burl Nyswonger <burl@nyswonger.org>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] stdout/stderr and CRLF translations...
Date: Thu, 23 Oct 2003 00:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0310220958460.841-100000@mx.nyswonger.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0310151333020.27998-100000@mx.nyswonger.org>
Hi,
I am having some trouble figuring out how to get my default console
to use /dev/tty0. I am using the PC architecture, and have set:
CYGDAT_IO_SERIAL_I386_PC_SERIAL0_NAME == "\"/dev/tty0\""
CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE == "\"/dev/tty0\""
I have the LIBC pacakge, SERIAL_DRIVERS, etc..
stdout/stderr work fine - I have confirmed that all stdio (in/out/err) is
actually using the serial serial device (interrupt driven, etc.) and not
the diag stuff...
I have tried to set up tty0 by getting a handle with
'cyg_io_lookup(devname, &handle)' - which does not return an error -
I then set |= the flags with 'CYG_TTY_OUT_FLAGS_CRLF' (even though
this is part of the default value).
What seems to be happening is that none of the stdin/stdout I/O is going
through 'tty_write()' in 'io/serial/current/src/tty.c', but rather through
'serial_write()' which is located in 'io/serial/current/src/common/serial.c'.
I've tried to force stdout/stderr to '/dev/tty0' with fclose()/fopen()
stdout - freopen(...,stdout), etc.. all to no avail...
If I try to use cyg_io_lookup() and cyg_io_write(), I get the same results
(and I have confirmed that the writes are still not going through
tty_write(), but rather serial_write())
If anyone can help out, I'd appriciate it!
-- Burl.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-10-23 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 3:49 [ECOS] Obtaining all entries from the routing table Burl Nyswonger
2003-10-16 7:25 ` Andrew Lunn
2003-10-23 0:28 ` Burl Nyswonger [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=Pine.LNX.4.21.0310220958460.841-100000@mx.nyswonger.org \
--to=burl@nyswonger.org \
--cc=ecos-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).