From: "Dustin Byford" <dustin@firein.net>
To: Jim Thompson <jim@musenki.com>, "Kerl, John" <John.Kerl@Avnet.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: custom mpc8240 student project (long)
Date: Thu, 21 Feb 2002 20:11:45 -0500 [thread overview]
Message-ID: <web-8961389@zipmail.com> (raw)
On Thu, 21 Feb 2002 14:32:32 -0600
Jim Thompson <jim@musenki.com> wrote:
>
> I can't begin to endorse just how true this is. The top
> of my
> keyboard/desk are littered with tiny dead flash parts.
> Our (8245)
> boards have had the sockets re-soldered at least 3 times
> each, due
> entirely to handling stress.
>
> Not mentioned is the fact that the pins eventually
> oxidize.
Fortunately I found a little zif to pga socket that I can
put in a wire wrap socket. If the pins start oxidizing
before this project is over I'm in trouble anyway.
--Dustin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-02-22 1:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 1:11 Dustin Byford [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 18:33 custom mpc8240 student project (long) Kerl, John
2002-02-22 20:51 ` Wolfgang Denk
2002-02-22 1:07 Dustin Byford
2002-02-21 20:12 Kerl, John
2002-02-21 20:32 ` Jim Thompson
2002-02-21 22:40 ` Ron Bianco
2002-02-22 9:32 ` Geir Frode Raanes
2002-02-22 13:09 ` Jerry Van Baren
2002-02-23 19:16 ` Dan Malek
2002-02-25 12:18 ` Geir Frode Raanes
2002-02-27 11:46 ` Christian Pellegrin
[not found] <7E8519F1A7C0D211B0D200A0C93AA60F08447D20@ntmail.iskratel.si>
2002-02-18 21:17 ` Dustin Byford
2002-02-18 21:44 ` Wolfgang Denk
[not found] ` <auto-000008693306@zipmail.com>
2002-02-18 22:32 ` Wolfgang Denk
2002-02-19 11:40 ` Jerry Van Baren
2002-02-19 16:53 ` Bob Piatek
2002-02-20 2:32 ` Greg Griffes
2002-02-18 10:33 Dustin Byford
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=web-8961389@zipmail.com \
--to=dustin@firein.net \
--cc=John.Kerl@Avnet.com \
--cc=jim@musenki.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.