linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: hp <aput99@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Development Environment:
Date: Tue, 20 Jan 2004 12:06:37 -0800	[thread overview]
Message-ID: <20040120200637.GB32018@gate.ebshome.net> (raw)
In-Reply-To: <20040120195133.50035.qmail@web20416.mail.yahoo.com>


On Tue, Jan 20, 2004 at 11:51:33AM -0800, hp wrote:
> I am doing a research on what are the "best" or "most popular" tools to use
> in an embedded linux development environment right now.  I know there are a
> lot of expert embedded linux developers in this news group.  I would really
> appreciated it if you would take a few seconds to let me know what you are
> using or what you think is good to use for the following:
>
>                   compiler: _________

GCC 2.95.3 (from MVL 2.1), plan to upgrade to 3.x series shortly

>                 deployment: _________

???? what do you mean ?

> code management (i.e. cvs): _________

Perforce

>            kernel debugger: _________

BDI, RiscWatch but mostly printk + custom kernel tracer similar to LTT.

>           bootrom debugger: _________

BDI, RiscWatch

I'm not sure these are the _best_ tools though :)

Eugene.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2004-01-20 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AAB0E96AD630DC4E8D751BA4D854F2A1074CB487@WKCORPXCH.corp.weekleyhomes.com>
2004-01-20 19:51 ` Development Environment: hp
2004-01-20 20:06   ` Eugene Surovegin [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=20040120200637.GB32018@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=aput99@yahoo.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).