From: Wolfgang Denk <wd@denx.de>
To: "Rolf Liu" <rolfl@sc.mcel.mot.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: why there is NOT support for FADS board ?
Date: Mon, 19 Feb 2001 18:57:31 +0100 [thread overview]
Message-ID: <20010219175736.E3A79281D9@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 19 Feb 2001 17:04:03 +0800." <033b01c09a52$e88f11e0$bf0102c8@sc.mcel.mot.com>
In message <033b01c09a52$e88f11e0$bf0102c8@sc.mcel.mot.com> you wrote:
>
> I can see supports for MBX, RPXLITE, RPXCLASSIC, etc.
> but why not FADS support in linux ppc ?
Speaking just for myself: I always like to work in environments where
the chance of hardware problems is minimal. I'm making mistakes
enough myself, so I don't need unreliable hardware as a compli-
cation. From what I've seen so far, I don't think the FADS board is
the most reliable piece of hardware around. It may have been even
worse, with improvements lately. I don't really know - and I don't
care any more. I've been burned once, that's enough.
I guess others feel similar.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Man is the best computer we can put aboard a spacecraft ... and the
only one that can be mass produced with unskilled labor.
-- Wernher von Braun
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-19 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 9:04 why there is NOT support for FADS board ? Rolf Liu
2001-02-19 17:57 ` Wolfgang Denk [this message]
2001-02-19 18:10 ` Dan Malek
2001-02-26 11:06 ` dynamic modification exception handler kerler
2001-02-26 18:35 ` David Edelsohn
2001-02-27 2:08 ` kerler
2001-03-01 3:49 ` kerler
2001-03-01 4:11 ` David Edelsohn
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=20010219175736.E3A79281D9@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rolfl@sc.mcel.mot.com \
/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).