From: Bart Veer <bartv@cygnus.co.uk>
To: deborah@best.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: eCos ports to CP1500 or other Sparc targets?
Date: Thu, 07 Oct 1999 05:36:00 -0000 [thread overview]
Message-ID: <199910071236.NAA24290@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <199910070019.RAA10347@shell5.ba.best.com>
>>>>> "Deborah" == Deborah Gronke Bennett <deborah@best.com> writes:
Deborah> I discovered eCos at ESC last week. I am curious whether
Deborah> you know of a planned or in-progress port to the CP1500,
Deborah> a compact-PCI card with uses the UltraSparcIIi processor?
Deborah> I'm also curious whether there are any other Sparc ports
Deborah> that you know of.
Cygnus is not doing any further Sparc ports at present, but there may
be ports happening on the net.
Deborah> p.s. You should fix the text part of the mailto: links on
Deborah> your webpage at
Deborah> http://sourceware.cygnus.com/ecos/faq.html#porting_does_it
Deborah> which point to ecos aliases at cygnus.com, not
Deborah> sourceware.cygnus.com.
Thanks. I fixed the ecos-discuss@cygnus.com mistake, left over from
before the mailing lists were moved. The other email address,
ecos-maintainers@cygnus.com rather than
ecos-maintainers@sourceware.cygnus.com, is correct at present.
The intention is to distinguish between private and public emails. If
people find that this is causing problems I can arrange for the latter
address to work as well (it might already do so).
Bart Veer // eCos net maintainer
next prev parent reply other threads:[~1999-10-07 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-06 17:19 [ECOS] " Deborah Gronke Bennett
1999-10-07 5:36 ` Bart Veer [this message]
1999-10-07 10:46 ` [ECOS] " Deborah Gronke Bennett
1999-10-07 10:56 ` 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=199910071236.NAA24290@sheesh.cygnus.co.uk \
--to=bartv@cygnus.co.uk \
--cc=deborah@best.com \
--cc=ecos-discuss@sourceware.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).