public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Chris Lesiak" <clesiak@licor.com>
To: ecos-discuss@cygnus.com
Subject: Re: [ECOS] eCos 1.1
Date: Fri, 22 Jan 1999 06:01:00 -0000	[thread overview]
Message-ID: <86256701.004D1FAD.00@hooper2.licor.com> (raw)

I don't have any answers (I also just started to look at the software,)
 but would like to add a question related to 5:

6. Is cygmon available as sourceware so that I can port it to my board?
(It is mentioned in the documentation that came with the sourceware, but
I could find only the binaries.)

Chris Lesiak
clesiak@env.licor.com
LI-COR, Inc.


             reply	other threads:[~1999-01-22  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-22  6:01 Chris Lesiak [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-01-21 20:29 Jimen Ching
     [not found] ` < 000201be45bf$6d7e33d0$65b7a8c0@JimenC.alii.com >
1999-01-27 10:55   ` Bart Veer

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=86256701.004D1FAD.00@hooper2.licor.com \
    --to=clesiak@licor.com \
    --cc=ecos-discuss@cygnus.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).