From: Scott Anderson <scott_anderson@mvista.com>
To: Felix Radensky <felix@allot.com>
Cc: Linix PPC Emmbedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BDI2000 vs RiskWatch
Date: Tue, 21 Aug 2001 10:37:12 -0700 [thread overview]
Message-ID: <3B829C48.64C5FCDF@mvista.com> (raw)
In-Reply-To: 3B8212A6.9AF31020@allot.com
Felix Radensky wrote:
> Can someone please explain what BDI2000 can do that RiskWatch cannot.
To me, the main thing is that it integrates well with a Linux
development box. I use my normal debug tools (ddd/gdb) and the BDI2000
acts like a gdbserver for the kernel. For things such as FLASHing code
into the target, you just telnet into the BDI2000.
Bottom line: If you are developing on Windows, the RiscWatch is probably
what you want. If you are developing on Linux (which I hope is the
case), you want a BDI2000. Otherwise, you're going to need a Windows
box for RiscWatch to run on and then you'll have to set up Samba or some
other mechanism for the Windows box/RiscWatch to see your sources, etc.
Scott Anderson
scott_anderson@mvista.com MontaVista Software Inc.
(408)328-9214 1237 East Arques Ave.
http://www.mvista.com Sunnyvale, CA 94085
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-21 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 7:49 BDI2000 vs RiskWatch Felix Radensky
2001-08-21 11:23 ` Wolfgang Denk
2001-08-21 11:15 ` Felix Radensky
2001-08-21 17:37 ` Scott Anderson [this message]
2001-08-22 10:46 ` Kenneth Johansson
-- strict thread matches above, loose matches on Subject: below --
2001-08-21 17:44 Wright, David
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=3B829C48.64C5FCDF@mvista.com \
--to=scott_anderson@mvista.com \
--cc=felix@allot.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).