[Xenomai-git] New commits on branch next

2018-04-19 Thread git repository hosting
URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=5e449ed0f8374fd333688f2a71a896d92e244783 Author: Jan Kiszka Date: Wed Apr 18 14:51:00 2018 +0200 cobalt/synch: Clear PP boost prior to handing over the ownership Otherwise we first add the synch

[Xenomai-git] Philippe Gerum : Revert "copperplate/heapobj-pshared: fix memory limit"

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: 63621418456fa55a7ce1825bbcc8550bc5c275a6 URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=63621418456fa55a7ce1825bbcc8550bc5c275a6 Author: Philippe Gerum Date: Thu Apr 19 19:18:28 2018 +0200 Revert

Re: [Xenomai] Call Alchemy API from a Posix skin thread

2018-04-19 Thread Yann le Chevoir
> On 04/19/2018 03:27 PM, Yann le Chevoir wrote: >> Hello, >> >> With Xenomai 3, I understood that all skins are based on Posix skin, >> right? >> >> I used to use Posix skin. >> I have a third party Alchemy API (I am wondering if it was well ported >> from Native to Alchemy or not...). >> >>

Re: [Xenomai] Call Alchemy API from a Posix skin thread

2018-04-19 Thread Philippe Gerum
On 04/19/2018 03:27 PM, Yann le Chevoir wrote: > Hello, > > With Xenomai 3, I understood that all skins are based on Posix skin, > right? > > I used to use Posix skin. > I have a third party Alchemy API (I am wondering if it was well ported > from Native to Alchemy or not...). > > Why can not I

Re: [Xenomai] Call Alchemy API from a Posix skin thread

2018-04-19 Thread Julien Blanc
Le jeudi 19 avril 2018 à 15:27 +0200, Yann le Chevoir a écrit : >  > I thought that both Alchemy and Posix skins would create a "Xenomai > thread" > and so I could mix the calls to API skins. You can mix the APIs, but not the descriptors (ie, don't rt_mutex_acquire a pthread_mutex_t). However, it

[Xenomai] Call Alchemy API from a Posix skin thread

2018-04-19 Thread Yann le Chevoir
Hello, With Xenomai 3, I understood that all skins are based on Posix skin, right? I used to use Posix skin. I have a third party Alchemy API (I am wondering if it was well ported from Native to Alchemy or not...). Why can not I call this API from my Posix skin? Is it an expected behavior?

Re: [Xenomai] [PATCH] copperplate: Drop PI from registry locks

2018-04-19 Thread Philippe Gerum
On 04/19/2018 11:24 AM, Jan Kiszka wrote: > On 2018-04-19 11:17, Philippe Gerum wrote: >> On 04/17/2018 09:30 AM, Jan Kiszka wrote: >>> On 2018-04-17 09:22, Philippe Gerum wrote: On 04/13/2018 07:51 PM, Jan Kiszka wrote: > None of the callers that run into the locks have RT requirements.

Re: [Xenomai] [PATCH] copperplate: Drop PI from registry locks

2018-04-19 Thread Jan Kiszka
On 2018-04-19 11:17, Philippe Gerum wrote: > On 04/17/2018 09:30 AM, Jan Kiszka wrote: >> On 2018-04-17 09:22, Philippe Gerum wrote: >>> On 04/13/2018 07:51 PM, Jan Kiszka wrote: None of the callers that run into the locks have RT requirements. Signed-off-by: Jan Kiszka

Re: [Xenomai] [PATCH] copperplate: Drop PI from registry locks

2018-04-19 Thread Philippe Gerum
On 04/19/2018 11:17 AM, Philippe Gerum wrote: > On 04/17/2018 09:30 AM, Jan Kiszka wrote: >> On 2018-04-17 09:22, Philippe Gerum wrote: >>> On 04/13/2018 07:51 PM, Jan Kiszka wrote: None of the callers that run into the locks have RT requirements. Signed-off-by: Jan Kiszka

Re: [Xenomai] [PATCH] copperplate: Drop PI from registry locks

2018-04-19 Thread Philippe Gerum
On 04/17/2018 09:30 AM, Jan Kiszka wrote: > On 2018-04-17 09:22, Philippe Gerum wrote: >> On 04/13/2018 07:51 PM, Jan Kiszka wrote: >>> None of the callers that run into the locks have RT requirements. >>> >>> Signed-off-by: Jan Kiszka >>> --- >>> >>> As noted before, I

[Xenomai-git] New commits on branch next

2018-04-19 Thread git repository hosting
URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=11be709384b4bd8b905a6416e54018c58be1ec0c Author: Jan Kiszka Date: Wed Apr 18 14:51:00 2018 +0200 cobalt/synch: Clear PP boost prior to handing over the ownership Otherwise we first add the synch

[Xenomai-git] Philippe Gerum : copperplate/heapobj-pshared: fix off-by-one error in pagemap reset

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: 5abb09dab0035263b0f6233d54795230cdb8f37e URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=5abb09dab0035263b0f6233d54795230cdb8f37e Author: Philippe Gerum Date: Thu Apr 19 11:01:49 2018 +0200

[Xenomai-git] Greg Gallagher : cobalt/rtdm: Increase RTDM_MAX_MINOR to 4096 form 1024

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: 0e0dee05a511e14139b8c1c1e25b84662feed4d3 URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=0e0dee05a511e14139b8c1c1e25b84662feed4d3 Author: Greg Gallagher Date: Thu Apr 19 06:14:00 2018 +0200 cobalt/rtdm: Increase

[Xenomai-git] Philippe Gerum : copperplate/heapobj-pshared: fix memory limit

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: 5b0c3677fa15397ab7d8e609685f8b4259d62fde URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=5b0c3677fa15397ab7d8e609685f8b4259d62fde Author: Philippe Gerum Date: Thu Apr 19 11:00:06 2018 +0200

[Xenomai-git] Philippe Gerum : scripts: histo.gp: fix spelling in label

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: e34036b36908eef04b1c788d6e53fdd4adfdb944 URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=e34036b36908eef04b1c788d6e53fdd4adfdb944 Author: Philippe Gerum Date: Thu Apr 19 10:15:10 2018 +0200 scripts: histo.gp: fix

[Xenomai-git] Philippe Gerum : drivers/gpio: mxc: look for imx7d devices

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: 2f07eda4df8d00b028c711fe94c7dc2091f6e4ff URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=2f07eda4df8d00b028c711fe94c7dc2091f6e4ff Author: Philippe Gerum Date: Thu Apr 19 10:22:02 2018 +0200 drivers/gpio: mxc: look

[Xenomai-git] Philippe Gerum : drivers/gpio: core: add OF-based scanner searching for multiple compat strings

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: a2262d5b85f35df485b726c93783a28336024850 URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=a2262d5b85f35df485b726c93783a28336024850 Author: Philippe Gerum Date: Thu Apr 19 10:21:01 2018 +0200 drivers/gpio: core: add

[Xenomai-git] Philippe Gerum : drivers/gpio: core: lock gpio_chip list while scanning for removal

2018-04-19 Thread git repository hosting
Module: xenomai-3 Branch: stable-3.0.x Commit: 144746346a118ac368935b8b9ea14f4677cf8e96 URL: http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=144746346a118ac368935b8b9ea14f4677cf8e96 Author: Philippe Gerum Date: Thu Apr 19 10:28:40 2018 +0200 drivers/gpio: core: lock

Re: [Xenomai] R: R: kernel panic - xenomai3.0.6

2018-04-19 Thread Jan Kiszka
On 2018-04-19 09:43, Fazio Maurizio wrote: > Hello Jan, > I really don't know what is happening... I'm trying to analyze the vmcore > file dump recorded with kdump. > I suppose that it happens because our application has a functionality that > calls some API of a driver for a PCI board installed

[Xenomai] R: R: kernel panic - xenomai3.0.6

2018-04-19 Thread Fazio Maurizio
Hello Jan, I really don't know what is happening... I'm trying to analyze the vmcore file dump recorded with kdump. I suppose that it happens because our application has a functionality that calls some API of a driver for a PCI board installed on the system... it seems that when this

Re: [Xenomai] mmap when using in conjunction with mapper to retrieve memory mapped IO space

2018-04-19 Thread Philippe Gerum
On 04/19/2018 01:02 AM, Pham, Phong wrote: > “This is likely happening because the default auto-init glue module for > a final executable is mentioned in the flags, you either want to pass > --auto-init-solib if you do need auto-init for bootstrapping a DSO, or > --no-auto-init if you don't care