From: "Tony@Blackhawk-DSP.com " <Tony@Blackhawk-DSP.com>
To: <jlarmour@redhat.com>, <elix@sources.redhat.com>,
<elix-announce@sources.redhat.com>
Subject: Re: EL/IX at ESC West! (Your email has been forwarded)
Date: Mon, 18 Sep 2000 13:42:00 -0000 [thread overview]
Message-ID: <s9c64585.064@mail.iewa.com> (raw)
Your email has been forwarded to Andrew Ferrari ( andrew@blackhawk-dsp.com ).
>>> elix 09/18/00 16:33 >>>
Red Hat will be attending the Embedded Systems Conference in San Jose
between 26th and 28th September. Come and see us at booth #1038!
Among other items, Red Hat will be demonstrating:
- the EL/IX API - see http://sources.redhat.com/elix
- Embedded Linux
- Redboot - the Red Hat Embedded Debug and Boot firmware
- new EL/IX-compatible additions to eCos, Red Hat's real-time operating
system for deeply embedded devices, as described at
http://sources.redhat.com/ecos
Red Hat technical experts will be available to answer all your queries.
Visit http://www.embedded.com/west/ for details of the conference and how
to sign up.
Jonathan Larmour
Red Hat
reply other threads:[~2000-09-18 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=s9c64585.064@mail.iewa.com \
--to=tony@blackhawk-dsp.com \
--cc=elix-announce@sources.redhat.com \
--cc=elix@sources.redhat.com \
--cc=jlarmour@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).