All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Vandenabeele <peter.vandenabeele@mind.be>
To: Alexander.J@lntinfotech.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Target CPU selection for Real time Embedded Linux
Date: Fri, 6 Dec 2002 02:41:10 +0100	[thread overview]
Message-ID: <20021206024109.S1931@mind.be> (raw)
In-Reply-To: <OFB8D7A27E.4DFEB42B-ON65256C86.003DE12F@lntinfotech.com>; from Alexander.J@lntinfotech.com on Thu, Dec 05, 2002 at 04:48:32PM +0530


On Thu, Dec 05, 2002 at 04:48:32PM +0530, Alexander.J@lntinfotech.com wrote:
>
> Hi all,
>
> We would like to build a Router software engine using Real Time Embedded
> linux.

The alternatives that immediately come to Mind are:

- Xilinx Virtex II Pro with Linux (Linux port posted 2 months ago and on ftp.mind.be)
- Intel IXP425 with Linux (Linux port expected Jan 2003)

I believe both those chips where targeted specifically to build
high-end, modern one-chip routing solutions. They have high speed
connections on them.

What is the bandwidth and number of interfaces you are targeting ?

> In this process, we need to freeze the target CPU. Could anyone help me in
> this regard?

In the telecom sector PowerPC is the standard (the optimized power consumption
of the ARM family is less relevant in switches; and PowerPC is high-performant).

XScale (ARM derived) is also a new performant platform that is available at
high frequencies in certain chips (80200 e.g.). Typical operation frequencies
of PowerPC405 and XScale in both chips are 300 MHz I believe.

Please note that the use of the FPGA created some very spectacular possibities,
such as the idea to build-in a wirespeed firewall in the FPGA logic, where you
could reprogram the rules through a reconfiguration of the FPGA filters (this
is not a SW firewall, but it is still reprogrammable).

Peter

> Thanks
> Alex
>

--
.--------------------------------------------------------.
|       Mind: Embedded Linux and eCos Development.       |
| Mind is looking for Embedded Linux and eCos Developers |
|--------------------------------------------------------|
| Peter Vandenabeele, CEO          email:  peter@mind.be |
| Mind (http://mind.be)            tel:  +32-16-30.96.66 |
| Vaartkom 11                      fax:  +32-16-30.96.44 |
| B-3000 Leuven, Belgium           gsm: +32-478-27.40.69 |
'--------------------------------------------------------'

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

  reply	other threads:[~2002-12-06  1:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 11:18 Target CPU selection for Real time Embedded Linux Alexander.J
2002-12-06  1:41 ` Peter Vandenabeele [this message]
2002-12-06 20:55   ` Peter Ryser
2002-12-10 23:18   ` Board specific info for no EEPROM case Prakash kanthi
2002-12-11  0:10     ` Matt Porter

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=20021206024109.S1931@mind.be \
    --to=peter.vandenabeele@mind.be \
    --cc=Alexander.J@lntinfotech.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.