Lambert
Sent: Thursday, April 12, 2018 8:30 AM
To: Christoph Schroeder; etherlab-users@etherlab.org
Subject: Re: [etherlab-users] Απ: AL status message 0x0036: "DC Sync0
Cycle Time"
On 12 April 2018 03:52, quoth Christoph Schroeder:
> reffering to the last question on this list regar
On 12 April 2018 03:52, quoth Christoph Schroeder:
> reffering to the last question on this list regarding a driver for the RasPi
> 3 and
> kernel 4.x, which driver are you actually using? I thought the native drivers
> don't work with newer kernels. I am currently using the native driver for
> e1
Hello Mike,
reffering to the last question on this list regarding a driver for the
RasPi 3 and kernel 4.x, which driver are you actually using? I thought
the native drivers don't work with newer kernels. I am currently using
the native driver for e1000e Intel cards on Debian Jessie (kernel 3.16)
Well I think you are right, I don't think either that the Xenomai dance worths
it. As for the driver, I'm not so sure, but I think it's not the only parameter
to the equation.
Thanks again,
Mike
Από: Jürgen Walter • DATATRONiQ
Στάλθηκε: Δευτέρα, 2 Απριλ
Hi Jurgen,
thanks for your reply. The current option I have beyond the preempt_rt patch is
the Xenomai framework (since RTAI I think is not very actively developed
nowadays, in contrast with Xenomai).
I have read some articles which say that the gain in the loop rate is not that
much consider
Hi Martin,
thanks for the advice. It seems to me that the hard real time RT-Preempt patch
cannot be avoided if I want to achieve my goal. I will keep that in mind and
probably
come back to that.
Thanks again,
Mike
Από: Mike Karam
Στάλθηκε: Πέμπτη, 8 Μα
Hi Jurgen,
thanks for your reply. I forgot to mention that I'm running the lowlatency
package of kernel 4.8.0-58. The thing is that,
the team wants 16.04 Ubuntu because of the ROS Kinetic development, so I don't
think I can use
a 3.x kernel (although last time I checked there is also a 4.x PREEM
