From: David Hawkins <dwh@ovro•caltech.edu>
To: Wolfgang Denk <wd@denx•de>
Cc: Leonid <Leonid@a-k-a•net>, linuxppc-embedded@ozlabs•org
Subject: Re: PCI target implementation on AMCC PPC CPUs
Date: Thu, 06 Sep 2007 16:39:24 -0700 [thread overview]
Message-ID: <46E08FAC.8000608@ovro.caltech.edu> (raw)
In-Reply-To: <20070906233021.59D1C247AF@gemini.denx.de>
Hi Wolfgang,
>> Freescale's technical (design) support is great, and they
>> (the software developers; Kim, Timur, etc) are actively
>> maintaining/contributing to git trees for u-boot and Linux.
>> If you can change processors, I'd recommend any Freescale
>> part over an AMCC part.
>
> But then, a lot of people with in-depth experience with AMCC
> processors hang out on the lists and on IRC, too. AMCC is pretty well
> supported at least as far as U-Boot and Linux (and the ELDK) go.
Thats good to know.
I was just trying to relay my experience with the two
company's support and with two comparable processors
(440EP vs MPC8349EA).
The nice thing about this group, and open-source in
general, is the 'open' part, everyone can share their
experiences :)
Cheers,
Dave
next prev parent reply other threads:[~2007-09-06 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 18:24 finding out the processor frequency Leisner, Martin
2007-09-06 18:43 ` Scott Wood
2007-09-06 19:15 ` Josh Boyer
2007-09-06 19:15 ` PCI target implementation on AMCC PPC CPUs Leonid
2007-09-06 20:15 ` David Hawkins
2007-09-06 23:30 ` Wolfgang Denk
2007-09-06 23:39 ` David Hawkins [this message]
2007-09-06 20:26 ` David Hawkins
2007-09-11 9:13 ` Matthias Fuchs
2007-09-11 17:32 ` David Hawkins
2007-09-11 18:17 ` David Hawkins
2007-09-12 7:17 ` Matthias Fuchs
2007-09-12 16:04 ` David Hawkins
[not found] <46E0B178.00C522.05513@m5-81.163.com>
2007-09-07 2:13 ` Leonid
2007-09-07 2:34 ` David Hawkins
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=46E08FAC.8000608@ovro.caltech.edu \
--to=dwh@ovro$(echo .)caltech.edu \
--cc=Leonid@a-k-a$(echo .)net \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=wd@denx$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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