On 12/15/2017 02:20 PM, Jan Kiszka wrote:
> On 2017-12-15 13:25, Leopold Palomo-Avellaneda wrote:
>> Hi,
>>
>> I forgot something more:
>>
>> On 15/12/17 12:04, Philippe Gerum wrote:
>>
>> [...]
>>>>
>>>> I guess that
On 12/15/2017 02:40 PM, Jan Kiszka wrote:
> On 2017-12-15 14:29, Philippe Gerum wrote:
>> On 12/15/2017 02:20 PM, Jan Kiszka wrote:
>>> On 2017-12-15 13:25, Leopold Palomo-Avellaneda wrote:
>>>> Hi,
>>>>
>>>> I forgot something m
On 12/15/2017 03:24 PM, Jan Kiszka wrote:
> On 2017-12-14 20:44, Philippe Gerum wrote:
>> On 12/14/2017 08:28 PM, Jan Kiszka wrote:
>>> Hi Philippe,
>>>
>>> something got broken with the exception path rework:
>>>
>>> [2.6194
On 12/15/2017 04:02 PM, Jan Kiszka wrote:
> On 2017-12-15 15:44, Philippe Gerum wrote:
>> On 12/15/2017 03:24 PM, Jan Kiszka wrote:
>>> On 2017-12-14 20:44, Philippe Gerum wrote:
>>>> On 12/14/2017 08:28 PM, Jan Kiszka wrote:
>>>>> Hi Philippe,
>&g
On 12/15/2017 05:45 PM, Philippe Gerum wrote:
> On 12/15/2017 04:02 PM, Jan Kiszka wrote:
>> On 2017-12-15 15:44, Philippe Gerum wrote:
>>> On 12/15/2017 03:24 PM, Jan Kiszka wrote:
>>>> On 2017-12-14 20:44, Philippe Gerum wrote:
>>>>> On 12/14/2017 0
On 12/15/2017 06:53 PM, Jan Kiszka wrote:
> On 2017-12-15 17:45, Philippe Gerum wrote:
>> On 12/15/2017 04:02 PM, Jan Kiszka wrote:
>>> On 2017-12-15 15:44, Philippe Gerum wrote:
>>>> On 12/15/2017 03:24 PM, Jan Kiszka wrote:
>>>>> On 2017-12-14 20:44,
On 12/15/2017 02:48 PM, Philippe Gerum wrote:
> On 12/15/2017 02:40 PM, Jan Kiszka wrote:
>> On 2017-12-15 14:29, Philippe Gerum wrote:
>>> On 12/15/2017 02:20 PM, Jan Kiszka wrote:
>>>> On 2017-12-15 13:25, Leopold Palomo-Avellaneda wrote:
>>>>
On 12/15/2017 01:25 PM, Leopold Palomo-Avellaneda wrote:
> Hi,
>
> I forgot something more:
>
> On 15/12/17 12:04, Philippe Gerum wrote:
>
> [...]
>>>
>>> I guess that there's something in the kernel config or somewhere in 3.x that
>>> affe
On 12/15/2017 06:53 PM, Jan Kiszka wrote:
> On 2017-12-15 17:45, Philippe Gerum wrote:
>> On 12/15/2017 04:02 PM, Jan Kiszka wrote:
>>> On 2017-12-15 15:44, Philippe Gerum wrote:
>>>> On 12/15/2017 03:24 PM, Jan Kiszka wrote:
>>>>> On 2017-12-14 20:44,
On 12/17/2017 12:01 AM, Andreas Glatz wrote:
>>
>> I pushed a pile of RTnet fixes in a WIP branch of the official repo
>> (wip/rtnet-fixes). Most of them address invalid direct references to
>> user memory from kernel space (instead of properly copying back and
>> forth via the copy_from/to_user in
On 12/17/2017 02:43 PM, samira elmadani wrote:
> Hello please I have a problem and I don't know if I must reinstall xenomai
> or what exactly,
>
> I have installed xenomai-2.6.4 and I can star it but the problem is that
> when I use ./latency I have as result only the first 3 lines
>
The 2.6.x se
On 12/17/2017 05:38 PM, Greg Gallagher wrote:
>
> I believe Arm64 is only in the next branch, but i'll leave that to someone
> else to confirm or correct.
That is correct.
>
> Greg
>
> Original Message
> From: g...@embeddedgreg.com
> Sent: December 17, 2017 10:24 AM
> To: yuboch...@live.c
Some news about the ongoing day-to-day work:
- the Xenomai repository is being rehosted to the gitlab facility
offered by Denx Software Engineering (thanks Wolfgang), which currently
mirrors the original tree. We are working at making the final repository
publicly accessible before Xmas. We are s
Sixteen years after Gilles and I founded the Xenomai project, time has
come for me to hand over the leadership to a contributor recognized for
his skills, bringing fresh ideas, and a creative roadmap.
Jan Kiszka has agreed to take over the Xenomai leadership gradually from
me. He will be ramping
Dual kernel systems such as Cobalt need Linux to exhibit a high-priority
execution stage, for running out of band co-kernel activities. This is
the purpose of the I-pipe layer, patched in the mainline kernel for
supporting Cobalt.
In order to keep pace with mainline Linux development, this mechan
Hi Andreas,
On 12/19/2017 11:17 AM, Andreas Glatz wrote:
>>
>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
>> Sun
>> Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
>>
>> I have created the packages and new kernel with the same configuration th
On 12/19/2017 11:46 AM, Andreas Glatz wrote:
I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
Sun
Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
I have created the packages and new kernel with the same configuration
>>>
On 12/14/2017 06:07 PM, John Allwine wrote:
> I'm using the latest machinekit image for the 3.8 kernel on the Beaglebone
> Black (
> https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz).
> It's using xenomai 2.6.3. I follow the steps
On 12/20/2017 07:49 AM, Peng Fan wrote:
> On Mon, Dec 18, 2017 at 10:26:28AM +0800, Peng Fan wrote:
>> Hi All,
>>
>> I compiled xenomai-next on my ARM64 platform, but met Max and Avg not
>> correct.
>> See below:
>>
>> ./cyclictest -a -t10 -n -p99 -c 0
>> # /dev/cpu_dma_latency set to 0us
>> polic
On 12/19/2017 11:17 AM, Andreas Glatz wrote:
>>
>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
>> Sun
>> Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
>>
>> I have created the packages and new kernel with the same configuration that
>> I had.
On 12/20/2017 11:17 AM, Philippe Gerum wrote:
> On 12/19/2017 11:17 AM, Andreas Glatz wrote:
>>>
>>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
>>> Sun
>>> Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
On 12/20/2017 11:19 AM, Philippe Gerum wrote:
> On 12/20/2017 11:17 AM, Philippe Gerum wrote:
>> On 12/19/2017 11:17 AM, Andreas Glatz wrote:
>>>>
>>>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from
>>>> Sun
>>>>
On 12/20/2017 06:49 PM, Lange Norbert wrote:
> >-Original Message-
> >From: Jan Kiszka [mailto:jan.kis...@siemens.com]
> >Sent: Dienstag, 19. Dezember 2017 19:57
> >To: Lange Norbert; Xenomai (xenomai@xenomai.org); Philippe Gerum
> >Subject: R
On 12/19/2017 07:57 PM, Jan Kiszka wrote:
> On 2017-12-19 14:44, Lange Norbert wrote:
>>
>> Problem persists in ipipe-core-4.9.51-x86-4, ipipe-4.4 kernel crashes at
>> boot (likely no good support for this SOC).
>> Used program is attached, it is being executed twice, once directly via
>> serial
Hi,
On 01/17/2018 11:24 AM, ruggero wrote:
> Hello Philippe,
> Bernard asked me to take care of the problem.
>> Hello Bernhard,
>>
>> On 01/15/2018 12:07 PM, Gaus Bernhard, Dr. Mergenthaler GmbH & Co. KG
>> wrote:
>>> Hello Philippe,
>>> Our elpc system a running quite well but we get some sporad
On 01/17/2018 05:38 PM, ruggero wrote:
> Hi Pilippe,
> a small addition: the driver compile when included directly in the
> kernel. Normally we would like to have it as a module.
>
diff --git a/arch/arm/kernel/ipipe.c b/arch/arm/kernel/ipipe.c
index 771bb5eff7fe..e0624d3f1ee2 100644
--- a/arch/ar
On 01/20/2018 02:51 PM, jimmyo wrote:
> Hello,
>
> we have a system with a imx6 processor and kernel 3.14 with xenomai
> 2.6.5 (native api)
>
> Now we plan to switch from kernel v3.14 to a newer kernel.
> I've seen that the last kernel ipipe supports is version 4.9.x.
> Are there any schedule for
/xenomai-3.git wip/rtnet-fixes
for you to review changes up to df4f825d1d8ab1b7129af59d43b3f219f4ae5101:
net/socket: forward private ioctl requests to NIC driver (2018-01-23 18:12:28
+0100)
Philippe Gerum (26):
net/cap: fix
Hi Jan,
On 01/23/2018 06:52 PM, Jan Kiszka wrote:
> Hi Philippe,
>
> as the number of question increase here, but I bet elsewhere as well,
> and I'm planning to work on some parts soonish, I'd like to coordinate:
>
> Where are we standing with 4.14 right now? There is nothing for x86 yet,
> rig
On 01/24/2018 09:44 AM, Leopold Palomo-Avellaneda wrote:
> Philippe,
>
>
> On 23/01/18 18:21, Philippe Gerum wrote:
>
>> For review by interested parties, proposed for inclusion in 3.0.6.
>
> 3.0.7 ?
>
Yep. Time is not moving
On 01/25/2018 02:43 PM, Julien Blanc wrote:
> Hi,
>
> We have a xenomai 3 application currently using the alchemy API
> (application development started on xenomai 2.x).
>
> We would like to add I/O multiplexing in some parts of the application.
> My understanding is that it is not supported by t
On 01/25/2018 04:14 PM, Julien Blanc wrote:
> Le jeudi 25 janvier 2018 à 15:21 +0100, Philippe Gerum a écrit :
>> On 01/25/2018 02:43 PM, Julien Blanc wrote:
>>>
>> There is no provision for I/O multiplexing with alchemy. Only the
>> pipe object embeds a RTDM
Here are some points I would like to discuss during this meeting. Please
feel free to comment:
1. Release management
* Currently, the person who contributes most of the code is also the
release manager, which is clearly not optimal. Both activities should be
decoupled for efficiency (esp
On 01/09/2018 11:35 PM, Henry Bausley wrote:
> We have an application that gets run repeatedly that causes a stack overflow.
> The source is at the end of this mail.
> We have tracked it down to changing the affinity.
>
> We have used xenomai 2.6.5 and 2.6.4 and kernels 3.14.28 and 4.1.18 and se
On 01/26/2018 07:32 PM, Jan Kiszka wrote:
> It can be confusing for people reading a trace when a context switch due
> to a wake up in the IRQ handler comes before the handler was left. Move
> the exit instrumentation before the schedule, just like we already do in
> the clock handler.
>
> Signed-
On 01/26/2018 07:49 PM, Jan Kiszka wrote:
>
> Then testing. I would also not go into too much details, but it would be
> good to understand what exist(ed) and what could be done easily to
> improve it.
That I can answer quickly: over the years, we went from manual testing I
was carrying out over
On 01/29/2018 07:01 PM, alessio margan wrote:
> Hi all,
>
> I was installing xenomai 3.0.6 (
> https://xenomai.org/downloads/xenomai/stable/ ) on a 4.9.51 kernel, I
> get the following errors
>
> drivers/xenomai/net/drivers/r8169.c:131:12: error: ‘debug’ redeclared as
> different kind of symbol
>
On 01/30/2018 07:59 AM, Jan Kiszka wrote:
> On 2018-01-30 01:26, Joonyoung Shim wrote:
>> Sometimes the kernel lockup occurs with "rtifconfig rteth0 down" command
>> execution on TDMA slave.
>>
>> [525182.648366] INFO: rcu_sched detected stalls on CPUs/tasks:
>> [525182.648372] 7-...: (0 ticks
On 01/31/2018 02:09 AM, Nihar Unadkat wrote:
> Hi
>
> I am using ipipe-ipipe-core-4.1.18-arm-9 which is patched with xenomai-2.6.5
>
> I am getting an error
> Xenomai: suspending kernel thread 7f8c2cb8 ('') at 0x7f89d6e8 after
> exception #0x8
>
> Where ('') is our function name.
>
>
On 01/31/2018 03:28 AM, Greg Gallagher wrote:
> This patch is based on one that was submitted by Wolfgang Netbal back in Feb
> 2016 but a formal patch was never submitted.
> I added a couple small changes (style errors and imx7 define) and tested on a
> imx7d board. One quick note, the IMX7D define
On 01/31/2018 03:36 AM, Greg Gallagher wrote:
> ---
> kernel/drivers/gpio/Kconfig | 10 +-
> kernel/drivers/gpio/Makefile | 3 ++-
> kernel/drivers/gpio/gpio-xilinx.c | 40
> +++
> 3 files changed, 51 insertions(+), 2 deletions(-)
[snip]
>
On 01/31/2018 03:36 AM, Greg Gallagher wrote:
> If the device name from the device tree starts with a forward slash (/) the
> rtdm device stores it in the registry including the forward slash. When we
> go to use that device and do the registry lookup we use a relative path from
> /dev/rtdm which
On 01/31/2018 03:36 AM, Greg Gallagher wrote:
> Some SOCs will have two GPIO chips that require two independent drivers. In
> my
> case I was working with the Zynq SOC and needed a driver for the gpios on the
> FPGA and a driver for the gpios available on the ARM core. This change allows
> for tw
On 02/01/2018 05:43 PM, Jan Kiszka wrote:
> Hi,
>
> it seems those functions above force the caller always to secondary mode
> (ok, panic is not an issue). Intentionally? To avoid using the wrapped
> versions which may trigger one of the calls again? Or could we also call
> the RT versions, at lea
On 02/02/2018 09:51 AM, Julien Blanc wrote:
I'm trying to use multiplexing wih rtcan sockets (using
xeno_can_flexcan driver).
Unfortunately, i had no luck yet to make it work. __RT(select) fails
with ENODEV error, while __RT(poll) returns a POLLERR event.
poll() is not implemented by libcobalt
On 02/05/2018 05:22 PM, Greg Gallagher wrote:
Hi,
After the recent meet up we had, I had an idea to help with a
couple of issues that we identified. One issue that was brought up is
new users don't know how to get started with Xenomai, this impacts the
community of users and downstream feedb
On 02/06/2018 05:09 AM, Greg Gallagher wrote:
Small fix ups to enable building multi_v7_defconfig
---
drivers/gpio/gpio-mvebu.c | 1 +
drivers/gpio/gpio-pl061.c | 1 +
drivers/gpio/gpio-zynq.c | 2 +-
drivers/irqchip/irq-atmel-aic5.c | 6 --
drivers/irq
On 02/05/2018 04:50 PM, Yann le Chevoir wrote:
Hello,
I am an engineering student and I try to proof that a 4000Hz hard real-time
application can run on an ARM board rather than on a more powerful machine.
I work with an IMX6 dual-core and Xenomai Cobalt 3.0.4. I use POSIX skin.
By the way, I f
On 02/09/2018 12:45 AM, Lowell Gilbert wrote:
> Am I correct in assuming that when calling rtdm_timer_start(), I should
> not be getting multi-second latencies before the first call to the timer
> routine? Just checking before I dig in too far.
>
Of course not. I suspect an absolute expiry time i
On 02/09/2018 11:02 AM, Philippe Gerum wrote:
> On 02/09/2018 12:45 AM, Lowell Gilbert wrote:
>> Am I correct in assuming that when calling rtdm_timer_start(), I should
>> not be getting multi-second latencies before the first call to the timer
>> routine? Just checking be
On 02/09/2018 03:14 PM, Henning Schild wrote:
> Hi,
>
> we have been seeing several issues with calling xenomai_init multiple
> times for the same skin. Once it was a segfault and another time was an
> issue related to the registry.
> I want to come up with patches for both cases, but i would like
On 02/09/2018 06:58 PM, Henning Schild wrote:
> Am Fri, 9 Feb 2018 18:23:47 +0100
> schrieb "[ext] Henning Schild" :
>
>> Am Fri, 9 Feb 2018 17:48:22 +0100
>> schrieb Jan Kiszka :
>>
>>> On 2018-02-09 17:13, Henning Schild wrote:
When using dlopen() to include xenomai libraries into an
On 02/11/2018 02:57 AM, Greg Gallagher wrote:
> I'm getting the raspberry pi zero images ready and I see the following
> in the dmesg:
>
> [0.00] WARNING: CPU: 0 PID: 0 at
> /home/ggallagher/devel/emb_linux/ipipe-arm/kernel/irq/chip.c:57
> irq_set_chip+0x7c/0xac
> [0.00] irqchip AR
On 02/09/2018 05:54 PM, Jan Kiszka wrote:
> From: Wolfgang Hartmann
>
> Use the __RT versions of the stdio function calls to avoid migration to
> secondary mode. In case of ___panic, flush the printer before exiting to
> avoid losing messages.
>
> Signed-off-by: Wolfgang Hartmann
> Signed-off-b
On 02/13/2018 01:38 PM, Henning Schild wrote:
> The first one actually fixes a regression where debian packages can not
> be generated anymore. And the remaining two fix minor issues.
>
> Henning Schild (3):
> debian: drop prebuild docs from packages
> debian: add mssing build dependency
> d
On 02/16/2018 02:13 PM, Henning Schild wrote:
> In order to fix a segfault in a dlopen()/dlclose()/dlopen() sequence i
> wrote a testcase to reproduce the issue. That testcase also covers a few
> other dlopen-related things.
> The testcase is intetgrated into smokey. Because a smokey-test is alread
On 02/26/2018 02:46 PM, branislav.sa...@automatika.imp.bg.ac.rs wrote:
> Hello,
>
> I have a problem with new I-pipe patch, which was not existing with legacy
> patch on 3.14 kernel, on BeagleBone platform.
>
> When GPIO pin is configured as input with edge interrupt enable, on IRQ
> occurrence t
On 02/26/2018 06:45 PM, Jan Kiszka wrote:
> From: Wolfgang Hartmann
>
> Use the __RT versions of the stdio function calls to avoid migration to
> secondary mode. In case of ___panic, flush the printer before exiting to
> avoid losing messages.
>
> Signed-off-by: Wolfgang Hartmann
> Signed-off-b
On 02/26/2018 10:41 PM, Giulio Moro wrote:
> git checkout stable-3.0.x
> scripts/bootstrap
> mkdir -p ../xenomai-3-build && cd ../xenomai-3-build
> ../xenomai-3/configure --with-core=cobalt --enable-pshared
> --host=arm-linux-gnueabihf --build=arm CFLAGS="-march=armv7-a -mfpu=vfp3"
> --enable-dlo
On 02/26/2018 10:34 PM, Julian Viereck wrote:
> Hi folks,
>
> after installing Xenomai 3.0.5/kernel 4.9.38 following [1] on our Dell
> Precision 5820 machine (Intel Xeon W-2145), there are high latencies
> when the system is at rest. When starting a stress test via `stress -v
> -c 8 -i 10 -d 8`, t
Gentlemen, we have 30 patches waiting for review by RTnet gurus in
wip/rtnet-fixes. We already had some positive feedback about them fixing
the ugly SMAP-related issue, which we may want to merge to stable-3.0.x
asap, but there are a couple of unrelated changes to review as well, namely:
9a6bbc38
On 02/28/2018 10:40 PM, Julian Viereck wrote:
> Thanks for your pointer to hwlatdetect and possible SMI issues.
>
> It looks like the hwlatdetect script is not working with the latest
> kernel anymore. However, it appears the hwlat is now part of the
> kernel's ftrace [1]. Here is the kernel docum
On 02/28/2018 08:36 PM, Jan Kiszka wrote:
> On 2018-02-28 19:24, Philippe Gerum wrote:
>>
>> Gentlemen, we have 30 patches waiting for review by RTnet gurus in
>> wip/rtnet-fixes. We already had some positive feedback about them fixing
>> the ugly SMAP-related issue, wh
On 02/21/2018 07:33 PM, Jan Kiszka wrote:
> Hi,
>
> likely due to some platform oddities (still has to be analyzed in more
> details), we are running into the situation that xntimer_grab_hardware
> on a x86-64 host tunes nkclock.wallclock_offset to a value that is not
> compatible with the 32-bit
On 03/01/2018 06:46 PM, Julian Viereck wrote:
>> 1) disable hyperthreading and running a single core
> Seems like the latency problem is due to enabled hyperthreading.
>
> I reran the latency tests with hyperthreading disabled and the latencies
> stay below 20 microseconds now. This is with 1 and
On 03/02/2018 02:22 PM, Henning Schild wrote:
> Moving the definition out of the ifdef solves the following error:
>
> include/xenomai/cobalt/kernel/clock.h:260:16: error:
> ‘struct ’ has no member named ‘adjust_time’
> include/xenomai/cobalt/kernel/clock.h:263:19: error:
> ‘struct ’ has no memb
On 03/08/2018 05:19 AM, Ivid Suvarna wrote:
> "commit 9da7bde" introduces rt_print_flush_buffers in ancillaries
>
> Fixes the following error "--with-core=mercury" :
>
>>> ancillaries.c: In function ‘___panic’:
>>> ancillaries.c:129:2: error: implicit declaration of function
> ‘rt_print_
On 03/08/2018 03:16 PM, Pintu Kumar wrote:
> Hi,
>
> On x86_64 machine (with xenomai 3.0) sometimes I observed a huge
> variance and inconsistency in latency data when measuring latency
> delay using clock_nanosleep.
> I observed this inconsistency in both normal kernel, as well as xenomai
> kern
On 03/10/2018 10:16 AM, Шевченко Тарас Григорьевич wrote:
> Now my new attempt
>
> git clone [ https://git.xenomai.org/xenomai-3.git |
> https://git.xenomai.org/xenomai-3.git ]
> git checkout stable-3.0.x
> cd xenomai-3
> ./script/bootstrap
> ./configure --with-pic --with-core=cobalt --enabl
On 03/10/2018 11:34 AM, Шевченко Тарас Григорьевич wrote:
>
>
> I cloned repo just yesterday
> and now this issue is not fixed
>
> so i decide to use xenomai-3.0.6.tar.bz2 and successfully install it
> /usr/xenomai/sbin# ./version
> Xenomai/cobalt v3.0.6
>
> ./xeno-config
> xeno-config --v
On 03/14/2018 11:42 AM, Julien Blanc wrote:
> Hi,
>
> The current xenomai documentation states that it is allowed to call
> clock_settime with CLOCK_REALTIME parameter to set the value of the
> xenomai realtime clock. On our board, the value at bootup is always 0
Assuming you run in dual kernel m
On 03/13/2018 12:33 PM, Schrenkhammer, Martin wrote:
> I am currently porting a project from Haswell to Skylake (i5-6440EQ). When in
> desktop, I observe latency peaks when windows are moved around or zoomed.
> With Haswell CPUs, there is not impact of graphic workload. Unfortunately
> everythin
On 03/08/2018 04:55 PM, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This both de-duplicates the code and ensures that all fields are zeroed
> prior to calling one of the actual tcb initialization functions.
> Specifically if host_task is not properly cleaned, we may cause a bug
> when using the fiel
On 03/15/2018 09:24 AM, Pintu Kumar wrote:
> Hi All,
>
> I am trying to test rt_cond_bind() and rt_task_unblock() API with a
> simple thread program using the Xenomai native skin, and with xenomai
> 3.0.6.
>
> But, during call to rt_task_unblock(&task1) from the main function, I
> get the segment
On 03/15/2018 10:51 AM, Pintu Kumar wrote:
> On Thu, Mar 15, 2018 at 2:08 PM, Philippe Gerum wrote:
>> On 03/15/2018 09:24 AM, Pintu Kumar wrote:
>>> Hi All,
>>>
>>> I am trying to test rt_cond_bind() and rt_task_unblock() API with a
>>> simple thre
On 03/15/2018 12:07 PM, Pintu Kumar wrote:
> On Thu, Mar 15, 2018 at 3:29 PM, Philippe Gerum wrote:
>> On 03/15/2018 10:51 AM, Pintu Kumar wrote:
>>> On Thu, Mar 15, 2018 at 2:08 PM, Philippe Gerum wrote:
>>>> On 03/15/2018 09:24 AM, Pintu Kumar wrote:
>>&g
On 03/15/2018 05:47 PM, Pintu Kumar wrote:
> Hi,
>
> Please find the complete program below:
Thanks. This is a Xenomai bug, most likely in libcopperplate. What your
test app tries to do is legit. The bug also triggers in native mode
(Mercury), so this is a generic issue. I'll follow up on this.
On 03/16/2018 10:49 AM, Pintu Kumar wrote:
> OK Thank you so much :)
>
Fixed by this commit from the -stable branch.
http://git.xenomai.org/xenomai-3.git/commit/?id=945c7dbf7c5ae19755a26b69d00f714176c87c4a
>
>
> I think this tests works on Xenomai 2.6 (some one else tested long
> back. Unfortun
On 03/16/2018 12:19 PM, Stéphane Ancelot wrote:
> Hi,
>
> I upgraded my applications to latest release (next branch) .
The next branch is by definition NOT released, this is a development tree.
>
> I do not manage to run the shared session , using session-label to run
> the program as user (fix
On 03/09/2018 05:51 PM, Jan Kiszka wrote:
> The following changes since commit 5618f90d33b17ab0ee9352705610a5e9f00f9964:
>
> Revert "ipipe: printk: defer dev_printk() output to safe context"
> (2017-12-15 18:10:01 +0100)
>
> are available in the git repository at:
>
> git://git.xenomai.org/
On 03/10/2018 11:06 PM, Jan Kiszka wrote:
> On 2018-03-09 08:51, Jan Kiszka wrote:
>> 4.9 requires more work, I've pushed the beginning to wip/4.9 in the same
>> repo.
>
> I started to patch further on this during my flight (wip/4.9 updated),
> noticed that the 4.14-wip queue will need a little bi
On 03/10/2018 11:06 PM, Jan Kiszka wrote:
> On 2018-03-09 08:51, Jan Kiszka wrote:
>> 4.9 requires more work, I've pushed the beginning to wip/4.9 in the same
>> repo.
>
> I started to patch further on this during my flight (wip/4.9 updated),
> noticed that the 4.14-wip queue will need a little bi
On 03/20/2018 08:26 AM, Pintu Kumar wrote:
> On Tue, Mar 20, 2018 at 10:57 AM, Pintu Kumar wrote:
>> On Tue, Mar 20, 2018 at 9:03 AM, Greg Gallagher
>> wrote:
>>> If you want to use open, read, write you need to specify in the
>>> makefile to use the posix skin. You need something like these in
On 03/20/2018 12:31 PM, Pintu Kumar wrote:
> On Tue, Mar 20, 2018 at 3:02 PM, Philippe Gerum wrote:
>> On 03/20/2018 08:26 AM, Pintu Kumar wrote:
>>> On Tue, Mar 20, 2018 at 10:57 AM, Pintu Kumar wrote:
>>>> On Tue, Mar 20, 2018 at 9:03 AM, Greg Gallagher
>&g
On 03/20/2018 12:31 PM, Pintu Kumar wrote:
> On Tue, Mar 20, 2018 at 3:02 PM, Philippe Gerum wrote:
>> On 03/20/2018 08:26 AM, Pintu Kumar wrote:
>>> On Tue, Mar 20, 2018 at 10:57 AM, Pintu Kumar wrote:
>>>> On Tue, Mar 20, 2018 at 9:03 AM, Greg Gallagher
>&g
On 03/20/2018 01:00 PM, Pintu Kumar wrote:
> On Tue, Mar 20, 2018 at 5:15 PM, Philippe Gerum wrote:
>> On 03/20/2018 12:31 PM, Pintu Kumar wrote:
>>> On Tue, Mar 20, 2018 at 3:02 PM, Philippe Gerum wrote:
>>>> On 03/20/2018 08:26 AM, Pintu Kumar wrote:
>>
On 03/20/2018 04:42 AM, Jan Kiszka wrote:
> On 2018-03-20 00:54, Philippe Gerum wrote:
>> On 03/10/2018 11:06 PM, Jan Kiszka wrote:
>>> On 2018-03-09 08:51, Jan Kiszka wrote:
>>>> 4.9 requires more work, I've pushed the beginning to wip/4.9 in the same
>>&g
On 03/10/2018 11:06 PM, Jan Kiszka wrote:
> On 2018-03-09 08:51, Jan Kiszka wrote:
>> 4.9 requires more work, I've pushed the beginning to wip/4.9 in the same
>> repo.
>
> I started to patch further on this during my flight (wip/4.9 updated),
> noticed that the 4.14-wip queue will need a little bi
3 which removes the buggy feature because of
> problems with the MMU.
No, the commit you are referring to reads as this:
commit 323824258692a6d175881d18a644b276858b353d
Author: Philippe Gerum
Date: Sat Nov 14 16:41:13 2015 +0100
cobalt/powerpc: drop support for unlocked context swi
On 03/22/2018 06:09 PM, PRADHAN, MAKARAND wrote:
> Hi All,
>
> I am working on upgrading our device from Xenomai 2 to Xenomai 3. I have been
> consulting the Xenomai web page. Based on reading the online documentation, I
> have a fair understanding of the UDD, All the same, I would highly apprec
On 03/24/2018 02:55 PM, Gabriel Aguirre-Ollinger wrote:
> Hi,
> I'm running Xenomai/cobalt v3.0.5 on an Intel(R) Celeron(R) CPU. Currently
> I'm writing a real-time task loop that requires execution to stop until a
> signal with a certain integer value is received. Thus I've included a call
> to rt
On 03/23/2018 01:40 PM, Pintu Kumar wrote:
> Dear Philippe,
>
> Thank you so much for your detailed explanation.
>
> First to cross-check, I also tried on ARM BeagleBone (White) with
> 256MB RAM, Single core
> These are the values I got.
After how many samples?
> ===
> N
Download:
https://xenomai.org/downloads/ipipe/v4.x/arm64/older/ipipe-core-4.9.51-arm64-4.patch
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
Download:
https://xenomai.org/downloads/ipipe/v4.x/arm/ipipe-core-4.9.51-arm-4.patch
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
Download:
https://xenomai.org/downloads/ipipe/v4.x/blackfin/ipipe-core-4.9.51-blackfin-3.patch
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
Download:
https://xenomai.org/downloads/ipipe/v4.x/x86/ipipe-core-4.9.51-x86-5.patch
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
Download:
https://xenomai.org/downloads/ipipe/v4.x/powerpc/ipipe-core-4.9.51-powerpc-3.patch
___
Xenomai mailing list
Xenomai@xenomai.org
https://xenomai.org/mailman/listinfo/xenomai
On 03/26/2018 03:12 PM, Pintu Kumar wrote:
> Dear Philippe,
>
> Thank you so much for your reply.
> Please find my comments below.
>
>
> On Sun, Mar 25, 2018 at 5:39 PM, Philippe Gerum wrote:
>> On 03/23/2018 01:40 PM, Pintu Kumar wrote:
>>> Dear Philippe
On 03/27/2018 09:59 AM, Frank Benkert wrote:
> Hello,
>
> we have to maintain an old productive system.
> It's based on a powerpc MPC5200.
> After updating Xenomai from 2.6.1 to 2.6.5 the Xenomai regression test
> suite failed on posix/mprotect:
>
> + /usr/bin/regression/posix/mprotect
> memory r
On 03/27/2018 02:09 PM, Pintu Kumar wrote:
> Hi,
>
> Thank you so much for all your explanation.
> But, before I dig deeper, I have some simple questions which is troubling me.
>
> 1) In Idle case, we see latency improvement (~2-3 micro-seconds on
> average) using Xenomai native task application,
301 - 400 of 3211 matches
Mail list logo
