linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Armin Steinhoff <armin@steinhoff.de>
To: dashesy <dashesy@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Recommended motherboard
Date: Tue, 03 May 2011 22:13:09 +0200	[thread overview]
Message-ID: <4DC061D5.30905@steinhoff.de> (raw)
In-Reply-To: <BANLkTinrbbV=8U8XDA1r+wNpbccVE7MsDQ@mail.gmail.com>


Hello Dashesy,

very good information are available at:

https://www.osadl.org/Individual-system-data.qa-farm-data.0.html#c4630

Check out the latency plots and make your own conclusion.

--Armin




dashesy wrote:
> I have tested the rt31 patch and everything seems great on my
> off-the-shelf high-end Xeon desktop so far. I will continue testing
> and let you know if I find any oopses or panics :)
>
> We are in the process of upgrading our embedded system, now based on
> an old ADEOS patch.
> In the first step we need to substitute our soon to be obsolete
> motherboard with a new long life industrial motherboard that works
> with -rt (as we all hope it will be all in the mainline).
> I know I will be going to a lengthy validation and testing phase to
> choose the right motherboard, one that is reliable (for a medical
> device), state-of-the-art (at least two cores) and of course -rt
> compliant (some indication about thing like SMI or hrtimer issues for
> example).
>
> There are few book and plenty of resources out there. "Building
> Embedded Linux Systems by Karim Yaghmour, et al" is a nice book, and
> linux-rt archives, LWN and LKML have been the ultimate source to keep
> up with the past (as much as I could) an learn the new. To find out
> what might cause problem or what to avoid when designing the system.
>
> It seems the manufacturers section of the OSADL Realtime QA Farm is a
> good starting point to look for motherboards if one is concerned about
> the latency plots, however,
> That would be great if there was some sort of -rt compliance
> certificate or tag, issued by OSADL (one organization that I can think
> of). I believe, this might generate some revenue for the project, and
> some ease of mind for developers who want to start a fresh design.
>
> I appreciate any comments or suggestion about the motherboard.
>
> Thanks
> dashesy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      parent reply	other threads:[~2011-05-03 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 18:05 Recommended motherboard dashesy
2011-05-03  8:42 ` Daniel James
2011-05-03 17:08   ` Ehsan Azarnasab
2011-05-03 20:13 ` Armin Steinhoff [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=4DC061D5.30905@steinhoff.de \
    --to=armin@steinhoff.de \
    --cc=dashesy@gmail.com \
    --cc=linux-rt-users@vger.kernel.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).