On Mon, 2019-01-14 at 10:39 +0100, Henning Schild wrote:
> Am Fri, 11 Jan 2019 14:47:13 +0100
> schrieb Mauro Salvini :
>
> > On Fri, 2019-01-11 at 10:40 +0100, Henning Schild wrote:
> > > Am Fri, 11 Jan 2019 09:57:50 +0100
> > > schrieb Mauro Salvini via Xenomai :
> > >
> > > > Hi all,
> > >
Am Fri, 11 Jan 2019 14:47:13 +0100
schrieb Mauro Salvini :
> On Fri, 2019-01-11 at 10:40 +0100, Henning Schild wrote:
> > Am Fri, 11 Jan 2019 09:57:50 +0100
> > schrieb Mauro Salvini via Xenomai :
> >
> > > Hi all,
> > >
> > > I'm testing same hardware of [1], with kernel 4.9.146 from ipipe-
Hi, Mauro
Thanks for your explanation, I will keeping tracing on this issue and
related code changes too.
Regards
Limingyu
On 1/11/19 9:51 PM, Mauro Salvini wrote:
On Fri, 2019-01-11 at 17:53 +0800, limingyu via Xenomai wrote:
Hi, Mauro
Maybe you could refer to this disscusion below, and
On Fri, 2019-01-11 at 17:53 +0800, limingyu via Xenomai wrote:
> Hi, Mauro
>
> Maybe you could refer to this disscusion below, and try the latesst
> stable xenomai code branch
>
> v3.0.x/stable.
> https://xenomai.org/pipermail/xenomai/2018-December/040086.html
>
> And the lasted xenomai code
On Fri, 2019-01-11 at 10:40 +0100, Henning Schild wrote:
> Am Fri, 11 Jan 2019 09:57:50 +0100
> schrieb Mauro Salvini via Xenomai :
>
> > Hi all,
> >
> > I'm testing same hardware of [1], with kernel 4.9.146 from ipipe-
> > 4.9.y
> > with [2] applied, compiled with ARCH=i386 and Xenomai 3.0.7.
>
Hi, Mauro
Maybe you could refer to this disscusion below, and try the latesst
stable xenomai code branch
v3.0.x/stable.
https://xenomai.org/pipermail/xenomai/2018-December/040086.html
And the lasted xenomai code is here:
https://gitlab.denx.de/Xenomai/xenomai/tree/stable/v3.0.x
On
Am Fri, 11 Jan 2019 09:57:50 +0100
schrieb Mauro Salvini via Xenomai :
> Hi all,
>
> I'm testing same hardware of [1], with kernel 4.9.146 from ipipe-4.9.y
> with [2] applied, compiled with ARCH=i386 and Xenomai 3.0.7.
To be honest i386 is not really tested anymore, in fact in 4.14 not
even
