quick survey only for PowerPC 405 folks

quick survey only for PowerPC 405 folks

[Christopher R. Johnson]

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. Kernel obtained from:

3. gcc version:
4. glibc version:
5. binutils version:

6. Did you build your own toolchain?
7. If not, where did it come from?
8. What is your development environment (editors, tools, debuggers, etc.)?
9. I have an Abatron, any useful magic I should know?
10. How do you manage building, configuring and delivering user-mode
software for the target?

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


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

Re: quick survey only for PowerPC 405 folks

[dank]

> 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/

Re: quick survey only for PowerPC 405 folks

[Eugene Surovegin]

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/

Re: quick survey only for PowerPC 405 folks

[Jon Masters]

Christopher R. Johnson wrote:

> 1. Kernel version:

Stock 2.4.23 + in house modifications.

> 2. Kernel obtained from:

UK kernel.org official mirror.

> 3. gcc version:

gcc-3.3.2 with some patches.

> 4. glibc version:

glibc-2.3.2 with some patches.

> 5. binutils version:

binutils-2.14.90.0.5

> 6. Did you build your own toolchain?

Yes using the crosstool however prior to that I had a rather painful
experience attempting to build it all up myself based on gcc 2.95
ultimately resulting in deciding DENX had done a better job (they seem
pretty good if you want to buy support too) than I had so...

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

Previously used DENX toolchain which was based upon gcc 2.95.

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

Editors - mostly emacs on various platforms with a little vi.
Tools - mostly gnu tools on Powerbook laptop running Debian although
also cross toolchain on Intel GNU/Linux. Xygwin and some Xilinx.
Debuggers - gdb and xmd mostly. Some custom stuff too.

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

You can send it to me if you want to :-).

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

Scripts and some stuff I will automate.

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

I was recently having problems with soft float on 405D however this
turned out to be a bug in the memory management code which has been
fixed since the release I had originally based my patches upon.
Upgrading seems to have solved that.

Floating point is being done via userspace library emulation however I
am compiling in the soft float support just in case.

Cheers,

Jon.


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