linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: dank@kegel.com
To: <cjohnson@gcctech.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: quick survey only for PowerPC 405 folks
Date: Wed, 3 Dec 2003 11:02:26 -0500 (EST)	[thread overview]
Message-ID: <2767.64.165.195.65.1070467346.squirrel@webmail.pair.com> (raw)
In-Reply-To: <3FCE04E3.9080602@gcctech.com>


> 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.4.17

> 2. Kernel obtained from:

linuxppc_dev_2_4
(but given the good reports about vanilla kernel.org 2.4.23,
maybe there's hope for ditching linuxppc_dev_2_4 eventually)

> 3. gcc version:

montavista hardhat 2.0's gcc 2.95 for kernel,
vanilla gcc 3.0.4 for apps,
but moving to gcc 3.3.2 for everything (though
that may be on hold until something forces them,
since I just left the company)

> 4. glibc version:

montavista hardhat 2.0's glibc-2.2.3,
but moving to glibc-2.2.5 or maybe glibc-2.3.2

> 5. binutils version:

oh, heck, I forget

> 6. Did you build your own toolchain?

yes, and I documented how I do it at http://kegel.com/crosstool
including workarounds for various compiler and glibc problems
like ppc405's friggin' erratum 77

> 7. If not, where did it come from?

we originally used montavista hardhat 2.0, still do
when building kernel, for the moment.

> 8. What is your development environment (editors, tools, debuggers,
> etc.)?

vi / emacs
gdb
oprofile (for ppc750, not sure if we have it running on pc405)
homebrew memory leak finder based on garbage collector

> 9. I have an Abatron, any useful magic I should know?

n/a.  I thankfully didn't have to do board bringup.

> 10. How do you manage building, configuring and delivering user-mode
> software for the target?

have custom makefiles for everything, but ready to
move to using ptxdist (http://ptxdist.sf.net)

> 11. Please pass along any comments on non-floating point -capable
> processors:

we were quite happy with ppc405 but have moved on to ppc750 etc
for new designs for integer performance.  Well, ok, erratum 77 sucked.

I'm no longer with the company in question, but
am still maintaining crosstool (though less intently)


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

  reply	other threads:[~2003-12-03 16:02 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 [this message]
2003-12-03 20:14 ` Eugene Surovegin
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=2767.64.165.195.65.1070467346.squirrel@webmail.pair.com \
    --to=dank@kegel.com \
    --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).