linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: sorin@nitechinc.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: dev boards comparison
Date: Tue, 26 Oct 1999 08:29:46 +0200	[thread overview]
Message-ID: <199910260629.IAA20848@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 25 Oct 1999 09:48:15 EDT." <99102509535300.00577@splash.nitechinc.com>


Hi Sorin,

in message <99102509535300.00577@splash.nitechinc.com> you write:
> 
> 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.

Which CPU are you looking for?

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

I had 2 *very* early (F)ADS boards, but then we were  using  some  30
MBX  boards  for the rest of the projects (not for Linux, but this is
not really important here)... Guess why.  If  your  only  choice  was
between FADS and MBX I would use the MBX. Just my $0.02 ...

> Are there other boards that might be considered?

Probably yes. I am using the mini modules by TQ  Systems  in  several
projects,  see http://www.tqs.de/HTM_Files/TQM8xx_Serie.htm for hard-
ware desriptions).

The TQ starter kit, which functionally is very  similar  to  the  MBX
board, is intentionally somewhat cheaper.

But IMHO an even more interesting feature is the  separation  of  the
"mini  module"  (containing  CPU,  RAM,  SRAM and FLASH memory, power
supply, etc.), from the rest of the framework needed to make a usable
configuration (mostly connectors). This results in a neat, very small
module (less than half a credit card!), that can be  used  as-is  for
your  final application - all you have to design is a (simple, cheap)
carrier  board  with  what  you  need  for  external  circuitry   and
connectors  etc.  I  always found it very convenient that development
and target system are more or less identical, at least from the soft-
ware point of view.


I ported Linux to those modules (including the latest 2.2.13 kernel),
and I have sent my patches to Dan Malek; I hope they will show up  in
one  of  the  next "standard" embedded kernels. I'm going to continue
supporting these modules, both for new CPU configurations and for new
options (like FLASH filesystem).

Feel free to contact me if this looks like an interesting  option  to
you.

Hope this helps,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Defaults are wonderful, just like fire.
                  - Larry Wall in <1996Mar6.004121.27890@netlabs.com>

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

      reply	other threads:[~1999-10-26  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-25 13:48 dev boards comparison Sorin Balea
1999-10-26  6:29 ` Wolfgang Denk [this message]

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=199910260629.IAA20848@denx.local.net \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=sorin@nitechinc.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).