From: Duane Ellis <duane_ellis@franklin.com>
To: insight@sources.redhat.com
Subject: Insight Developer type people.
Date: Thu, 13 Jul 2000 19:31:00 -0000 [thread overview]
Message-ID: <200007140231.WAA20325@mercury.franklin.com> (raw)
Ok,
I've been working on something now for a while. We might be looking
for some assistance with finishing a custom Insight port. (The main
port is done *NOW* using an earlier snapshot version of insight but,
there's a varity of things that still need to be done.)
1) Who at Red Hat do I contact about contract work on Insight?
I'd like a phone number of a human.
2) Are there any contractors types out there who are available to do
contract work on insight. (Even better if you are in the southern
New Jersey. See our web site for a more detailed location)
This involves a full simulation of a custom risc cpu, custom mmu,
etc. Simulated LCD display, and other tid bits (of course, Insight is
current debugger/simulator for the SDK, gcc is the compiler, but not
gas or ld - they did not have the feature set we needed)
--Duane.
for more info about what we do, and what I've been working on please
see our web site.
http://www.franklin.com
http://www.zdnet.com/zdtv/freshgear/products/story/0,3679,2596552,00.html
reply other threads:[~2000-07-13 19:31 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=200007140231.WAA20325@mercury.franklin.com \
--to=duane_ellis@franklin.com \
--cc=insight@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).