From: Wolfgang Denk <wd@denx.de>
To: "Omanakuttan" <omanakuttan@tataelxsi.co.in>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: bdi200 or powertap.. help me to decide.
Date: Thu, 09 Jan 2003 09:30:32 +0100 [thread overview]
Message-ID: <20030109083037.88D89C608E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 09 Jan 2003 10:06:45 +0530." <3E1CFC5D.5030608@tataelxsi.co.in>
In message <3E1CFC5D.5030608@tataelxsi.co.in> you wrote:
>
> I have been following the recent ( and ongoing ) discussions on bdi2000.
> I have recommended the company to buy bdi2000. The company is
> considering bdi2000 and powertap. ( AMC Applied Microsystems
> Corporation's PowerTAP™).
> I am going through the data sheet of powertap and doing a comparitative
> study of both products to find out which one is better suited for linux
> kernel debugging. Frankly we don't need any of the jazz that powertap +
> MWX-ICE™ debugger offers .We will be happy to use GNU tools. One good
> feature I see in powertap is to examine the contents of the registers.
> but I am a little pessimistic about the linux kernel debug support on
> powertap.
Ask yourself (and your AMC / Metrowerks sales guy) the following
questions:
* Does the PowerTAP documentation / sales guys claim to support Linux
as target OS? Especially is the MMU support good enough to debug
for example dynamically loaded kernel modules?
* How many people on this mailing list actually reported that they
have successfully used a PowerTAP to debug the Linux kernel
including dynamically loaded device drivers?
* Is there support for Linux as host OS?
* Does the Linux kernel provide special hooks for the PowerTAP
(equivalent to the CONFIG_BDI_SWITCH configuration option)?
* Which CPUs are supported by the PowerTAP? The BDI2000 supports
CPU32/32+, ColdFire, PowerPC, ARM, MIPS32, XScale and M-CORE ...
Guess what we're using...
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
I wish I had a bronze torc for every user who didn't read the manual.
- Terry Pratchett, _The Light Fantastic_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-01-09 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 4:36 bdi200 or powertap.. help me to decide Omanakuttan
2003-01-09 8:30 ` Wolfgang Denk [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=20030109083037.88D89C608E@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=omanakuttan@tataelxsi.co.in \
/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).