[etherlab-users] 答复: [SPAM] etherlab-users Digest, Vol 106, Issue 6

2016-04-14 Thread shouqiang.yao
Hi, All: When I use the interface function: ecrt_slave_config_dc(sc1, 0x0730, 25, 0, 175, 0); I can't understand the parameter "SYNC0 shift time" used in the master module, in the master modules code , the "SYNC0 shift time" is used in function "ec_fsm_slave_config_state_dc_sync_check"

Re: [etherlab-users] 答复: [SPAM] etherlab-users Digest, Vol 106, Issue 6

2016-04-14 Thread Gavin Lambert
On Friday, 15 April 2016 13:49, quoth shouqiang@scbd.com.cn: > When I use the interface function: ecrt_slave_config_dc(sc1, 0x0730, > 25, 0, 175, 0); > > I can't understand the parameter "SYNC0 shift time" used in the master > module, in the master modules code , the "SYNC0 shift

[etherlab-users] 答复: [SPAM] etherlab-users Digest, Vol 106, Issue 6

2016-04-14 Thread shouqiang.yao
Hi, All: When I use the interface function: ecrt_slave_config_dc(sc1, 0x0730, 25, 0, 175, 0); I can't understand the parameter "SYNC0 shift time" used in the master module, in the master modules code , the "SYNC0 shift time" is used in function "ec_fsm_slave_config_state_dc_sync_check"

[etherlab-users] 答复: [SPAM] etherlab-users Digest, Vol 106, Issue 6

2016-04-14 Thread shouqiang.yao
Hi, All: When I use the interface function: ecrt_slave_config_dc(sc1, 0x0730, 25, 0, 175, 0); I can't understand the parameter "SYNC0 shift time" used in the master module, in the master modules code , the "SYNC0 shift time" is used in function "ec_fsm_slave_config_state_dc_sync_check"

Re: [etherlab-users] Distributed Clocks

2016-04-14 Thread Thomas Bitsky Jr
>>Although we have not experienced these issues and are successfully using this >>driver, Is that to say you are using the E1000e driver? Do you modify its configuration at all? Tom (Sent from my mobile device.) On Apr 14, 2016, at 5:16 PM, Richard Hacker >

Re: [etherlab-users] Distributed Clocks

2016-04-14 Thread Richard Hacker
On 14.04.2016 23:51, Thomas Bitsky Jr wrote: Over the course of the last few weeks, I have done the following: - Built and installed a Xenomai 2.6.4 kernel. - Switched x86 hardware - Adapted the program to Xenomai - Rewrote the program so that it is completely asynchronous - Fixed the