All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Brunner <dbrunner@ebus.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] I-pipe patches for x86
Date: Mon, 18 Aug 2014 17:42:46 -0700	[thread overview]
Message-ID: <53F29D86.7010809@ebus.com> (raw)
In-Reply-To: <53F1E305.1000300@xenomai.org>

On 08/18/2014 04:27 AM, Gilles Chanteperdrix wrote:
> On 08/18/2014 12:19 AM, Doug Brunner wrote:
>> Hi all,
>>
>> I'm in the midst of upgrading the software stack for an embedded
>> controller based on a WinSystems PPM-LX800 (was previously Xeno 2.6.1
>> and Linux 3.2). I see there are I-pipe patches out for 3.10.32 and 3.14,
>> as well as the 3.8.13 included with Xenomai 2.6.3. This is going in a
>> road vehicle and so the priority is on stability over the security
>> offered by the newer Linux (it should only rarely be connected to a
>> network and never to the Internet.) What's your impression of the
>> stability of the newer versions vs. 3.8?
>>
>> Thanks,
>>       Doug Brunner
> Hi Doug,
>
> as maintainers, we try and test each version, and fix the issues we find
> until delivery. So, from our point of view, they are all equally stable,
> and it is difficult to answer your question. One detail however: you
> will not be able to run Xenomai 2.6.3 on Linux 3.14, you will need the
> upcoming Xenomai 2.6.4 for that. Xenomai 2.6.4 is expected to be
> delivered in the next few weeks.
>
> Regards.
>
Thanks Gilles, sounds like it will be worth waiting for 2.6.4 before 
making another transition. From the maintainers' perspective I was 
thinking mostly of "did 3.10/3.14 seem more troublesome/likely to break 
than 3.8 when you were writing and testing it?". I take it from your 
reply that it didn't, and I didn't see any reports of issues in the list 
archives...so when 2.6.4 is ready I will give it and 3.14 a go.

I also saw your tip on the CS5536 boot param and the benchmark results 
in your other email. Thanks for that, seems to work fine on my system.

     --Doug Brunner


  reply	other threads:[~2014-08-19  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17 22:19 [Xenomai] I-pipe patches for x86 Doug Brunner
2014-08-18 11:27 ` Gilles Chanteperdrix
2014-08-19  0:42   ` Doug Brunner [this message]
2014-08-18 22:46 ` Gilles Chanteperdrix

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=53F29D86.7010809@ebus.com \
    --to=dbrunner@ebus.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.