All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Mell" <mell@hedrich-winders.com>
To: Carsten Emde <Carsten.Emde@osadl.org>
Cc: esn@terma.com, linux-rt-users@vger.kernel.org
Subject: Re: Which version of preempt_realtime to use?
Date: Mon, 19 Jan 2009 21:45:58 +0100	[thread overview]
Message-ID: <4974E686.60105@hedrich-winders.com> (raw)
In-Reply-To: <49748567.30201@osadl.org>

>
> Esben,
>
>   
>> I am going to suggest that we use preempt_realtime for a _real_ project
>> (i.e. costumers will depend on it). We will run on standeard x86 (maybe
>> x86_64) hardware and will only need serial interfaces for realtime
>> purposes. Security is not an issue. Which version of preempt_realtime
>> should I pick?
>>     
> The latest and greatest *and* most stable version is 2.6.24.7-rt26. As
> far as I know (but maybe others know better), there are no unresolved
> issues with this "Latest Stable". The kernel release 2.6.24 may not
> contain sufficient architecture support for PPC and ARM, but the large
> majority of x86 based processors and chipsets is well supported.
>
> Please report, if anything does not work as expected.
>   
The only thing which is missing for me from the 2.6.24.7-rt series is
the patch
"x86-fpu-fix-config_preempt-y-corruption-of-application-s-fpu-stack.patch"
, GIT commit
 870568b39064cab2dd971fe57969916036982862 from mainline 2.6.25. This
might cause trouble with applications which are using floating point
arithmetics. Otherwise I am using the 2.6.24.7-rt series on a machine
control for a 16 axes machine and it is working mostly well. There are
only some points where I get big delays (up to some milliseconds) with
my timer routine, where normally delays are below 50 microseconds. Up to
now I could not find the application ( X ??) which is causing this.

Bye,
           Jürgen

-- 
Jürgen Mell (Software-Entwicklung)           mell@hedrich.com
Tel.:  +49-511-762-18226                     http://www.hedrich.com
FAX :  +49-511-762-18225
Mobil: +49-160-7428156
--------------------------------------------------------------------------------
HEDRICH winding systems GmbH
An der Universität 2 (im PZH)
D-30823 Garbsen (GERMANY)
--------------------------------------------------------------------------------
Geschäftsführer: Karsten Adam, Markus Gerth, Friedrich Frech
Handelsregister: Wetzlar, HRB 4768
Steuernr.: 020/235/20110                     USt-IdNr.: DE 258258279
-------------------------------------------------------------------------------- 

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

  reply	other threads:[~2009-01-19 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 12:01 Which version of preempt_realtime to use? Esben Nielsen
2009-01-19 13:51 ` Carsten Emde
2009-01-19 20:45   ` Jürgen Mell [this message]
2009-01-20  7:49     ` Robert Schwebel
2009-01-20  8:30       ` Pradyumna Sampath
2009-01-25 11:08         ` Thomas Gleixner
2009-01-22  7:40     ` Esben Nielsen
2009-01-22  8:37       ` Jürgen Mell
2009-01-28 19:32       ` Jürgen Mell

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=4974E686.60105@hedrich-winders.com \
    --to=mell@hedrich-winders.com \
    --cc=Carsten.Emde@osadl.org \
    --cc=esn@terma.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 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.