Hi,
I'm finishing up my work on a patch to add a RTDM gpio driver for
the zynq-7000 platform. I ran into a situation where I needed to call
gpio_request in gpio-core because the zynq gpio driver uses the
gpio_request function to enable the gpio pins on the board.
A side effect that I found
> Hi Steven,
>
> I have remote access to many ppc boards and could help here. This said
> 85xx, 40x and 44x already cover much of the ppc32 scope running Xenomai
> - maybe adding mpc52xx would be good, I have one here. I don't see much
> traction these days for Xenomai over ppc64, so I'm not even
On 11/23/2017 09:36 PM, Philippe Gerum wrote:
On 11/23/2017 01:38 PM, Jorge Ramirez wrote:
Xenomai also lacks an IRC channel which makes things way too quiet for a
small size community (in the case of ffmpeg for instance IRC is where
most if not all the discussions happen). IRC is - and should
On 11/23/2017 01:38 PM, Jorge Ramirez wrote:
> Xenomai also lacks an IRC channel which makes things way too quiet for a
> small size community (in the case of ffmpeg for instance IRC is where
> most if not all the discussions happen). IRC is - and should be for
> Xenomai- a good place to ask for
On Thu, Nov 23, 2017 at 01:38:03PM +0100, Jorge Ramirez wrote:
> In the past year alone I have been contributing to uboot (as board
> maintainer), arm-trusted-firmware (board maintainer), ffmpeg (v4l2 support),
> zephyr (multiple drivers), the linux kernel (some fixes), AOSP (fixes) and a
> few
On 11/22/2017 09:27 PM, Jan Kiszka wrote:
> On 2017-11-22 16:32, Philippe Gerum wrote:
>>
>> Hi Kendall,
>>
>> On 11/21/2017 08:27 PM, Auel, Kendall wrote:
>>> Hi Philippe,
>>>
>>> Is there an online bug tracking and feature request database? This would be
>>> a useful way to distribute work and
On 2017-11-23 14:18, Jorge Ramirez wrote:
> On 11/23/2017 01:52 PM, Henning Schild wrote:
>> Am Thu, 23 Nov 2017 12:42:08 +0100
>> schrieb Philippe Gerum :
>>
>>> On 11/22/2017 09:27 PM, Jan Kiszka wrote:
On 2017-11-22 16:32, Philippe Gerum wrote:
> Hi Kendall,
>
On 11/23/2017 04:15 PM, Leopold Palomo-Avellaneda wrote:
> On 23/11/17 16:12, Philippe Gerum wrote:
>> On 11/23/2017 04:08 PM, Leopold Palomo-Avellaneda wrote:
>>> On 23/11/17 16:04, Philippe Gerum wrote:
On 11/23/2017 03:58 PM, Leopold Palomo-Avellaneda wrote:
> On 23/11/17 13:22,
On 23/11/17 16:12, Philippe Gerum wrote:
> On 11/23/2017 04:08 PM, Leopold Palomo-Avellaneda wrote:
>> On 23/11/17 16:04, Philippe Gerum wrote:
>>> On 11/23/2017 03:58 PM, Leopold Palomo-Avellaneda wrote:
On 23/11/17 13:22, Philippe Gerum wrote:
> On 11/23/2017 01:10 PM, Leopold
On 11/23/2017 04:08 PM, Leopold Palomo-Avellaneda wrote:
> On 23/11/17 16:04, Philippe Gerum wrote:
>> On 11/23/2017 03:58 PM, Leopold Palomo-Avellaneda wrote:
>>> On 23/11/17 13:22, Philippe Gerum wrote:
On 11/23/2017 01:10 PM, Leopold Palomo-Avellaneda wrote:
> Hi,
>
>
> I
On 23/11/17 16:04, Philippe Gerum wrote:
> On 11/23/2017 03:58 PM, Leopold Palomo-Avellaneda wrote:
>> On 23/11/17 13:22, Philippe Gerum wrote:
>>> On 11/23/2017 01:10 PM, Leopold Palomo-Avellaneda wrote:
Hi,
I have seen this bug before, but it seems that it's again in 3.0.6.
On 23/11/17 15:58, Leopold Palomo-Avellaneda wrote:
> On 23/11/17 13:22, Philippe Gerum wrote:
>> On 11/23/2017 01:10 PM, Leopold Palomo-Avellaneda wrote:
>>> Hi,
>>>
>>>
>>> I have seen this bug before, but it seems that it's again in 3.0.6. Running
>>> 3.0.6 with:
>>>
>>> xeno-config --info
>>>
On 11/23/2017 03:58 PM, Leopold Palomo-Avellaneda wrote:
> On 23/11/17 13:22, Philippe Gerum wrote:
>> On 11/23/2017 01:10 PM, Leopold Palomo-Avellaneda wrote:
>>> Hi,
>>>
>>>
>>> I have seen this bug before, but it seems that it's again in 3.0.6. Running
>>> 3.0.6 with:
>>>
>>> xeno-config
On 11/23/2017 03:35 PM, Cédric Perles wrote:
>>> Hi,
>>>
>>> I’m working on an iMX6 based board with NXP kernel 4.1.15.
>
>>> Vendor kernels for i.MX6 are creepy (another vowel comes to mind). A
>>> recent mainline kernel is just fine if the SoC supports it. If not,
>>> porting the SoC (and/or
>> Hi,
>>
>> I’m working on an iMX6 based board with NXP kernel 4.1.15.
>> Vendor kernels for i.MX6 are creepy (another vowel comes to mind). A
>> recent mainline kernel is just fine if the SoC supports it. If not,
>> porting the SoC (and/or missing driver) to mainline is often much >
>>
At Bela (bela.io) we use Xenomai on the BeagleBone Black for audio. Currently
our resources are pretty scarce, but hopefully from March things should get
better For instance, now that RobertCNelson has discontinued support for
Xenomai on the BeagleBone, we may be able to help with that
On 11/23/2017 01:52 PM, Henning Schild wrote:
Am Thu, 23 Nov 2017 12:42:08 +0100
schrieb Philippe Gerum :
On 11/22/2017 09:27 PM, Jan Kiszka wrote:
On 2017-11-22 16:32, Philippe Gerum wrote:
Hi Kendall,
On 11/21/2017 08:27 PM, Auel, Kendall wrote:
Hi Philippe,
Is there
Am Thu, 23 Nov 2017 12:42:08 +0100
schrieb Philippe Gerum :
> On 11/22/2017 09:27 PM, Jan Kiszka wrote:
> > On 2017-11-22 16:32, Philippe Gerum wrote:
> >>
> >> Hi Kendall,
> >>
> >> On 11/21/2017 08:27 PM, Auel, Kendall wrote:
> >>> Hi Philippe,
> >>>
> >>> Is there an
On 11/23/2017 12:42 PM, Philippe Gerum wrote:
On 11/22/2017 09:27 PM, Jan Kiszka wrote:
On 2017-11-22 16:32, Philippe Gerum wrote:
Hi Kendall,
On 11/21/2017 08:27 PM, Auel, Kendall wrote:
Hi Philippe,
Is there an online bug tracking and feature request database? This would be a
useful way
On 11/23/2017 01:10 PM, Leopold Palomo-Avellaneda wrote:
> Hi,
>
>
> I have seen this bug before, but it seems that it's again in 3.0.6. Running
> 3.0.6 with:
>
> xeno-config --info
> Xenomai version: Xenomai/cobalt v3.0.6
> Linux bmm3 4.9.51-xenomai-3.0.6-ipipe #1 SMP Thu Nov 23 09:03:27 CET
Am Wed, 22 Nov 2017 21:26:23 +0100
schrieb Jan Kiszka :
> On 2017-11-21 18:11, Philippe Gerum wrote:
> > So, let's talk about the elephant in the room: the current
> > situation of the Xenomai project is not viable in the long run. I
> > can only encourage people who feel
Hi,
I have seen this bug before, but it seems that it's again in 3.0.6. Running
3.0.6 with:
xeno-config --info
Xenomai version: Xenomai/cobalt v3.0.6
Linux bmm3 4.9.51-xenomai-3.0.6-ipipe #1 SMP Thu Nov 23 09:03:27 CET 2017 x86_64
GNU/Linux
Kernel parameters:
On 11/23/2017 08:29 AM, Leopold Palomo-Avellaneda wrote:
> On 21/11/17 14:00, Norbert Lange wrote:
>> Hello,
>>
>> enabling RTNet will result in compile failures, because there is a
>> nameclash from some linux-headers.
>> This patch fixes some intel NICs to compile
>
> I have applied this patch
On 11/21/2017 02:00 PM, Norbert Lange wrote:
> Hello,
>
> enabling RTNet will result in compile failures, because there is a
> nameclash from some linux-headers.
> This patch fixes some intel NICs to compile
Merged, thanks.
--
Philippe.
___
Xenomai
Module: xenomai-3
Branch: stable-3.0.x
Commit: 3fb574cd1b69487c20f58b56332e0858032c6f21
URL:
http://git.xenomai.org/?p=xenomai-3.git;a=commit;h=3fb574cd1b69487c20f58b56332e0858032c6f21
Author: Norbert Lange
Date: Tue Nov 21 11:57:28 2017 +0100
rtnet/driver: fix
Hi Steven,
On 11/22/2017 05:49 PM, Steven Seeger wrote:
> Philippe, as we have previously discussed I am willing to take over the PPC i-
> pipe maintenance on my personal time if it will help.
Thanks, that would be great.
My only issue is right
> now the only PPC board I have in my
On 11/22/2017 01:33 PM, Leopold Palomo-Avellaneda wrote:
[snip]
>
> And finally, if you let me talk about our Elmer.
>
> The I/O frameworks are IMHO are crucial. It has a very limited scenario to
> develop a RT system if it has no interaction with the external devices, or
> whatever. I have
1.
https://github.com/pocoproject/poco/blob/develop/Foundation/src/Mutex_POSIX.cpp:64
2. mailto:beomjins@samsung.com
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL:
<http://x
28 matches
Mail list logo