From: Sorin Balea <sorin@nitechinc.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: dev boards comparison
Date: Mon, 25 Oct 1999 09:48:15 -0400 [thread overview]
Message-ID: <99102509535300.00577@splash.nitechinc.com> (raw)
Hello all
We're in the process of deciding which board to use for the
developement of our embedded products... we have now a
FADS 860 board... but we aren't that much impressed by it.
So can anyone please tell me which one is better from the
point of view of developing embedded solutions based on
Linux?
We are considering the FADS, along with the MBX boards
from Motorola and the RPX boards from Embedded Planet
Any pros and cons for this boards?
Are there other boards that might be considered?
>From what i now right now, i think the MBX is better...
Best regards
Sorin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-25 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-25 13:48 Sorin Balea [this message]
1999-10-26 6:29 ` dev boards comparison Wolfgang Denk
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=99102509535300.00577@splash.nitechinc.com \
--to=sorin@nitechinc.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).