All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@domain.hid>
To: Saul <xeno@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] PC suggestions for visual control
Date: Tue, 18 Apr 2006 15:29:15 -0400	[thread overview]
Message-ID: <44453E0B.8030509@domain.hid> (raw)
In-Reply-To: <1145337376.31480.259295744@domain.hid>

Saul wrote:
> Hi,
>
> I would be interested in hearing from people about the PC's that you use
> that are known to work well with Xenomai. I'd be looking for a fast new
> desktop PC for image processing and aircraft control tasks. Is AMD a
> better bet?
>
> Any suggestions much appreciated.
>
> Saul.
>
>   


Can you describe the workload a bit more fully ?

images - size, bpp, FPS, processing tasks ( FFTs, blurring, convolving, 
smoothing, etc) ?
control tasks - latency reqs, control-loop frequency,

I recall hearing that RTAI can run at audio rates (44 khz),
but its unclear what the workload is (small FIRs IIRs ??)
RTAI plays some 'tricks' that are counter to xenomai's goals
of clean, tight integration with linux, so it may not get the same khz 
numbers.

since you said FAST, you should look at a dual-core -
this gives you some room to assign your workloads to the cores,
thus better controlling context switching.  This could be important
for your image processing task thruput, and for latency too, since
the rt tasks wont have to reclaim the cpu just to resume their work.


BTW - I cant help but observe:
Id be leery of recommending any PC architecture for autopilot duties on 
an Airbus A-380.
Maybe its just the MS legacy dragging down the ole  PC-XT reputation ;-)
Ctrl-Alt-Delete is not an option :-D


  reply	other threads:[~2006-04-18 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18  5:16 [Xenomai-help] PC suggestions for visual control Saul
2006-04-18 19:29 ` Jim Cromie [this message]
2006-04-19  1:58   ` Saul

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=44453E0B.8030509@domain.hid \
    --to=jim.cromie@domain.hid \
    --cc=xeno@domain.hid \
    --cc=xenomai@xenomai.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.