From: Eugene Surovegin <ebs@ebshome.net>
To: "Christopher R. Johnson" <cjohnson@gcctech.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: quick survey only for PowerPC 405 folks
Date: Wed, 3 Dec 2003 12:14:10 -0800 [thread overview]
Message-ID: <20031203201410.GB30768@gate.ebshome.net> (raw)
In-Reply-To: <3FCE04E3.9080602@gcctech.com>
On Wed, Dec 03, 2003 at 10:44:35AM -0500, Christopher R. Johnson wrote:
>
> I'm trying to stabilize some tools and OS components, and would like
> your recommendations - you can reply directly to me if you like.
> Thanks! Currently my target processors are 200mHz 405GP and 333mHz
> 405GPr on a custom-designed board. We are already running 2.4.23-rc1 on
> the board with our own bootstrap.
>
> 1. Kernel version:
2.4.21
> 2. Kernel obtained from:
linuxppc-2.4 BK tree + some custom stuff
> 3. gcc version:
2.95.3
> 4. glibc version:
2.2.3
> 5. binutils version:
2.10.91
> 6. Did you build your own toolchain?
No
> 7. If not, where did it come from?
MVL 2.1
> 8. What is your development environment (editors, tools, debuggers, etc.)?
p4, gdb, ddd, Abatron, RiscWatch, brain :)
> 9. I have an Abatron, any useful magic I should know?
Usual stuff for any hw debugger. Nothing Abatron specific
> 10. How do you manage building, configuring and delivering user-mode
> software for the target?
>
Build: rather complex make + some Perl scripts
Delivery:
a) production: rpm + custom update daemon
b) development: NFS mount, or rsync, or scp, or whatever particular
developer prefers.
Eugene.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-03 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 15:44 quick survey only for PowerPC 405 folks Christopher R. Johnson
2003-12-03 16:02 ` dank
2003-12-03 20:14 ` Eugene Surovegin [this message]
2003-12-08 17:23 ` Jon Masters
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=20031203201410.GB30768@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=cjohnson@gcctech.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).