public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: tty.cdl
Date: Sun, 27 Mar 2011 21:11:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1103272357390.5121@sg-laptop> (raw)
In-Reply-To: <4D8F963A.6050501@siva.com.mk>

On Sun, 27 Mar 2011, Ilija Kocho wrote:

> Sergei, I started this discussion in order to discuss this issue before
> I drop any code. Your proposal sounds rational. I shall open a Bug and
> reference this discussion.

Ilija and may be not :-) I've seen that io_serial.h has

#ifdef CYGDAT_IO_SERIAL_DEVICE_HEADER
# include CYGDAT_IO_SERIAL_DEVICE_HEADER
#endif

So, your issue can be managed on the target's side, as both and tty.c
and termios.c include this header. You can add CDL component in your HAL
config file which parent should be CYGPKG_IO_SERIAL_TTY and define extra
devices (TTY4, TTY5, ...) there. Also define/set your own value for the
CYGDAT_IO_SERIAL_DEVICE_HEADER in the HAL's config file.


Sergei

  reply	other threads:[~2011-03-27 21:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 10:22 tty.cdl Ilija Kocho
2011-03-26 18:33 ` tty.cdl Sergei Gavrikov
2011-03-27 11:40   ` tty.cdl Ilija Kocho
2011-03-27 12:45     ` tty.cdl Sergei Gavrikov
2011-03-27 15:46       ` tty.cdl Ilija Kocho
2011-03-27 17:11         ` tty.cdl Sergei Gavrikov
2011-03-27 19:34           ` tty.cdl Ilija Kocho
2011-03-27 19:39             ` tty.cdl Sergei Gavrikov
2011-03-27 19:55               ` tty.cdl Ilija Kocho
2011-03-27 21:11                 ` Sergei Gavrikov [this message]
2011-03-28 10:42                   ` tty.cdl Ilija Kocho
2011-03-28 12:16                     ` tty.cdl Sergei Gavrikov
2011-03-28 19:00                       ` tty.cdl Ilija Kocho
2011-03-28 19:25                         ` tty.cdl Sergei Gavrikov

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=alpine.DEB.2.00.1103272357390.5121@sg-laptop \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    /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).