On 09/02/2015 02:43 AM, Don Mahurin wrote:
> ipipe - ipipe-3.14.44-arm64
>
This branch is available as is, as devel/ipipe-3.14.44-arm64 in the
mainline tree.
Thanks,
--
Philippe.
___
Xenomai mailing list
Xenomai@xenomai.org
http://xenomai.org/mailma
On 08/27/2015 05:37 PM, Jan Kiszka wrote:
> The following changes since commit b115c4094d734e19fa7a96be1bf3958b3d244b8b:
>
> Revert "ipipe: Register function tracer for direct and exclusive
> invocation" (2015-08-27 17:22:39 +0200)
>
> are available in the git repository at:
>
> git://git.x
On 09/02/2015 11:22 PM, Don Mahurin wrote:
> Pull request for xenomai-3/arm64, fixing tracing/syscall prints for arm64.
>
> The following changes since commit ef3d72d9825eb5ce3a75b93b6b4b4104f7c41db0:
>
> cobalt/arm64: machine.h: use slightly faster ffnz implementation
> (2015-06-17 16:09:20 -0
On 09/07/2015 01:53 PM, Konstantinos Chalas wrote:
> Hello everyone,
>
> Does any of you have a working implementation of timer_create( ) in
> Xenomai-3?
>
> According to the documentation /only thread-directed notification is
> supported (evp->sigev_notify set to//SIGEV_THREAD_ID//). The thing i
Hello everyone,
Does any of you have a working implementation of timer_create( ) in
Xenomai-3?
According to the documentation /only thread-directed notification is
supported (evp->sigev_notify set to//SIGEV_THREAD_ID//). The thing is
that the use of //SIG/EV_THREAD_ID is not common, therefor
On Mon, Aug 31, 2015 at 09:08:49AM +0200, Gilles Chanteperdrix wrote:
> On Mon, Aug 31, 2015 at 08:37:38AM +0200, Gilles Chanteperdrix wrote:
> > Hi,
> >
> > according to xenomai.org server statistics, some xenomai users are
> > mirroring xenomai.org git repositories. In order to make things
> > e
Hi Wolfgang,
On 09/07/2015 09:36 AM, Wolfgang Grandegger wrote:
> Hi Philippe,
>
> Am 04.09.2015 um 18:18 schrieb Philippe Gerum:
>>
>> We have a problem with CAN control requests piggybacking on struct ifreq
>> for passing arguments to the raw driver. This is unsafe, since we have
>> no mean to
Hi Philippe,
Am 04.09.2015 um 18:18 schrieb Philippe Gerum:
We have a problem with CAN control requests piggybacking on struct ifreq
for passing arguments to the raw driver. This is unsafe, since we have
no mean to relate sizeof(ifr.ifr_ifru) to the actual size required to
pass the CAN-related
Can I ask for review and merge of this work?
- Michael
> Am 21.07.2015 um 19:13 schrieb Steve Battazzo :
>
> From: SteveB
>
> ---
> ksrc/drivers/can/Kconfig |7 +
> ksrc/drivers/can/Makefile |6 +-
> ksrc/drivers/can/c_can/Kconfig
