Module: xenomai-2.6
Branch: master
Commit: f0a7b116faab75f732b611e0ba99b9b6ea7ce0ea
URL:
http://git.xenomai.org/?p=xenomai-2.6.git;a=commit;h=f0a7b116faab75f732b611e0ba99b9b6ea7ce0ea
Author: Wolfgang Grandegger w...@denx.de
Date: Tue Jan 15 16:22:02 2013 +0100
rtdm_iomap_to_user: fix
On 2013-01-16 07:55, John Morris wrote:
On 01/14/2013 08:07 AM, Philippe Gerum wrote:
On 01/14/2013 01:05 PM, Michael Haberler wrote:
Is there any chance somebody runs Xenomai AND RT_PREEMPT patches
applied? I heard a rumor but havent actually seen that
Yes, this works. The current target is
On 01/16/2013 08:37 AM, Wolfgang Grandegger wrote:
On 01/15/2013 08:46 PM, Gilles Chanteperdrix wrote:
On 01/15/2013 04:22 PM, Wolfgang Grandegger wrote:
From: Wolfgang Grandegger w...@denx.de
Pages mapped by rtdm_iomap_to_user() might be cached and may
page fault on the first write. At
On 2013-01-16 09:02, Jan Kiszka wrote:
At the same time, upstream should not pull or pick in
a way that makes life harder for downstream.
Philippe, in the future, please keep your public tree up-to-date,
ideally at a daily base. I'm seeing commits there that were done locally
more than a week
On 01/16/2013 09:44 AM, Jan Kiszka wrote:
On 2013-01-16 09:02, Jan Kiszka wrote:
At the same time, upstream should not pull or pick in
a way that makes life harder for downstream.
Philippe, in the future, please keep your public tree up-to-date,
ideally at a daily base. I'm seeing commits
On Wednesday 16 January 2013, Gilles Chanteperdrix wrote:
I may jump to 3.6, at least for the ARM architecture. As for the
backports to 3.4, I still intend to re-release 2.6.2, so, it would be
nice to backport the bugfixes in the core-3.5 branch to the core-3.4
branch.
If you plan on updating
On 01/16/2013 10:48 AM, Jan Kiszka wrote:
On 2013-01-16 10:41, Philippe Gerum wrote:
On 01/16/2013 09:44 AM, Jan Kiszka wrote:
On 2013-01-16 09:02, Jan Kiszka wrote:
At the same time, upstream should not pull or pick in
a way that makes life harder for downstream.
Philippe, in the future,
On 2013-01-16 13:03, Gilles Chanteperdrix wrote:
On 01/16/2013 11:37 AM, Philippe Gerum wrote:
What happened is a misunderstanding between Gilles and myself on the
presence of a pending pull request, nothing more, which eventually led
to an out-of-sync pulling on my end. Since this
On 01/16/2013 04:14 PM, Jan Kiszka wrote:
Hi Philippe,
a first heads-up, maybe you have an idea before I start debugging: That
patch causes troubles when our application shuts down. The main thread
hangs like this, unkillable:
It looks like the LO_WAKEUP_REQ virtual interrupt does not reach
On 2013-01-16 16:30, Jan Kiszka wrote:
On 2013-01-16 16:25, Philippe Gerum wrote:
On 01/16/2013 04:14 PM, Jan Kiszka wrote:
Hi Philippe,
a first heads-up, maybe you have an idea before I start debugging: That
patch causes troubles when our application shuts down. The main thread
hangs like
On 01/16/2013 11:59 AM, Yogi wrote:
Stephan Kappertz stephan.kappertz at kabelmail.de writes:
Hi Stephan,
I saw that you got Xenomai running on the Beaglebone from the thread here:
http://www.xenomai.org/pipermail/xenomai/2012-July/000476.html
I was wondering if you would be
In the legacy use case, __ipipe_switch_tail will be invoked over the
non-root domain after hardening. So clearing of TASK_HARDENING must not
be restricted to root.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
For the case my analysis was right. With this, Xenomai 2.6 works again
here.
12 matches
Mail list logo
