All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Question regarding rt_sem_p
Date: Sun, 14 Sep 2014 09:40:08 +0200	[thread overview]
Message-ID: <54154658.7030006@xenomai.org> (raw)
In-Reply-To: <54150B08.5070603@xenomai.org>

On 09/14/2014 05:27 AM, Gilles Chanteperdrix wrote:
> On 09/14/2014 04:44 AM, Lennart Sorensen wrote:
>> On Fri, Sep 12, 2014 at 10:54:21PM +0200, Gilles Chanteperdrix wrote:
>>> On 09/12/2014 10:52 PM, PRADHAN, MAKARAND (RC-CA) wrote:
>>>> Small correction:
>>>>
>>>> The ipipe patch that we are using is derived from ipipe-3.12.0 branch.
>>>
>>> This means a patch that has not even been tested. It just fixes merge
>>> conflicts, and has been compile checked, it has not run on real
>>> hardware. The one which has been tested on real hardware is the I-pipe
>>> patch for 3.14.0 or 3.14.17.
>>
>> Well 3.12 did pass the xenomai testsuite.
>>
>> Unfortunately TI isn't quite done moving their patches to the 3.14
>> branch yet, so we are still stuck at 3.12 (And the 3.8 branch was way
>> too unstable to use for anything at all even before considering xenomai).
>> Problem with new chips is that they aren't merged into the official
>> kernel yet, so jumping to a new kernel version isn't trivial.
>>
>> I will be checking if the 3.14 branch has enough to boot on Monday
>> (A lot of stuff was merged in yesterday so it might be getting close now).
>>
> I am almost sure I fixed an issue with user-space getting -EINTR with
> gdb. I simply did not want to look for the commit if you still have the
> issue with 3.14. If 3.14 does not boot, it looks like I will have to
> search the commit anyway.
> 

Could be this one, which also fixed a spurious assertion trigger:
http://git.xenomai.org/ipipe.git/commit/?h=ipipe-3.14&id=d7a5e4762535f55bfff8eafbf1c1dde214d09bd6

-- 
Philippe.


  reply	other threads:[~2014-09-14  7:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 20:33 [Xenomai] Question regarding rt_sem_p PRADHAN, MAKARAND (RC-CA)
2014-08-05 21:23 ` Gilles Chanteperdrix
     [not found]   ` <1410537098.19920.YahooMailNeo@web142606.mail.bf1.yahoo.com>
2014-09-12 20:35     ` PRADHAN, MAKARAND (RC-CA)
2014-09-12 20:38       ` Gilles Chanteperdrix
2014-09-12 20:52       ` PRADHAN, MAKARAND (RC-CA)
2014-09-12 20:54         ` Gilles Chanteperdrix
2014-09-14  2:44           ` Lennart Sorensen
2014-09-14  3:27             ` Gilles Chanteperdrix
2014-09-14  7:40               ` Philippe Gerum [this message]
2014-09-14 15:05                 ` Gilles Chanteperdrix
2014-09-15 15:09                   ` PRADHAN, MAKARAND (RC-CA)
2014-09-16 15:56               ` Lennart Sorensen
2014-09-16 17:52                 ` Jan Kiszka
2014-09-18 16:49             ` Lennart Sorensen

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=54154658.7030006@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --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.