From: Bart Veer <bartv@redhat.com>
To: rcc@jennic.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ARM Multi-ICE support status
Date: Mon, 09 Oct 2000 06:31:00 -0000 [thread overview]
Message-ID: <200010091330.e99DUwk24779@sheesh.cygnus> (raw)
In-Reply-To: <NDBBLOIOMLKELOJBAPAGKELPCBAA.rcc@jennic.com>
>>>>> "Robert" == Robert Cragie <rcc@jennic.com> writes:
Robert> Sorry if it's a bit off topic... can anyone tell me the
Robert> latest on the GDB ARM Multi-ICE support status? I am very
Robert> keen to use this!
This work depends on some header files etc. which belong to ARM. Red
Hat and ARM have been working together to get the relevant files
released under a license which is compatible with gdb's GPL. The exact
schedule is in ARM's hands, but I have been advised that it is
"imminent".
Bart Veer // eCos net maintainer
prev parent reply other threads:[~2000-10-09 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 6:10 Robert Cragie
2000-10-09 6:31 ` Bart Veer [this message]
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=200010091330.e99DUwk24779@sheesh.cygnus \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=rcc@jennic.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).