# Test result show below:
```
[ 59.778342] RTcfg: rtcfg_do_main_event() rtdev=1,
event=RTCFG_CMD_ADD, stateG
Waiting for all slaves...[ 59.868079] RTcfg: rtcfg_do_main_event()
rtdev=1, eG
[ 60.37] RTcfg: error -11 while sending stage 1 frame
```
We change the e1000_main.c line
for the specific board you are using.
Greg
On Mon., Nov. 12, 2018, 2:20 a.m. duanwujie via Xenomai
mailto:xenomai@xenomai.org> wrote:
On the arm64 already have ipipe patch , but the Xenomai not properly
worked on the arm64.
In order to support arm64, what other work needs to be done! Can
On the arm64 already have ipipe patch , but the Xenomai not properly
worked on the arm64.
In order to support arm64, what other work needs to be done! Can you
provide some clues?
On the arm64 already have ipipe patch , but the Xenomai not properly
worked on the arm64.
In order to support arm64, what other work needs to be done! Can you
provide some clues?
Hi, Phi and Jan:
I have question about synchronization object.Consider under condition.
*
*
*Thread A*
mutex_lock(lock) //O1
...
...
mutex_unlock(lock)//O2
*Thread B*
mutex_lock(lock) //O3
mutex_unlock(lock);
O1: become xnsynch's owner.
Hi, Phi and Jan:
The correct handler is handle_percpu_irq !
Hi, Phi and Jan:
I try to port the ipipe to mips arch according the
https://gitlab.denx.de/Xenomai/xenomai/wikis/Porting_Xenomai_To_A_New_Arm_SOC#terminology
Now it worked on the single cpu,but SMP
It seem to forget port the arch/x86/include/asm/fpu/internal.h in the
ipipe-core-4.9.135-x86-7.patch
在 2018/12/6 下午3:00, Jan Kiszka via Xenomai 写道:
On 06.12.18 06:45, limingyu via Xenomai wrote:
I have used this patch(ipipe-core-4.9.135-x86-7.patch) for a test
usage and I got a machine halt
ion fpregs_state *active_fpstate(struct fpu *fpu)
{
return >state;
}
#endif
在 2018/12/6 下午3:06, Jan Kiszka 写道:
On 06.12.18 08:04, duanwujie wrote:
It seem to forget port the arch/x86/include/asm/fpu/internal.h in the
ipipe-core-4.9.135-x86-7.patch
You mean that file is missing in the generated
Okay we will try and do other's test! thank you!
在 2018/12/6 下午3:26, Jan Kiszka 写道:
On 06.12.18 08:24, duanwujie wrote:
We use the xenomai 3.0.7 stable version. Is okay for this ?
No, as I said. You need the latest stable/3.0.x branch because you
need adjustments to the FPU changes
We use the xenomai 3.0.7 stable version. Is okay for this ?
在 2018/12/6 下午3:21, Jan Kiszka 写道:
On 06.12.18 08:18, duanwujie wrote:
I am not so sure, bellow code exist in ipipe-core-4.9.51-x86-2.patch
but ipipe-core-4.9.135-x86-7.patch didn't。
arch/x86/include/asm/fpu/internal.h:
#ifdef
We test the ipipe-core-4.9.135-x86-7 with the latest branch
stable/v3.0.x but the same error occur !
在 2018/12/6 下午3:26, Jan Kiszka 写道:
On 06.12.18 08:24, duanwujie wrote:
We use the xenomai 3.0.7 stable version. Is okay for this ?
No, as I said. You need the latest stable/3.0.x branch
Here is my test case:
Install debian 9.6 in virtual machine(virtualbox).
- Case 1: Build ipipe kernel(4.9.146) with debian's kerner default
config, when use this kernel to bootup system, click hibernate
button(This condition will be failed)
- Case 2: Build ipipe kernel(4.14.134)
So far, I haven't had any use cases yet, but I don't think interrupt
mechanisms should affect hibernate and wake up. And want to figure it out!
在 2019/10/17 下午1:52, Per Oberg 写道:
- Den 17 okt 2019, på kl 2:56, xenomai xenomai@xenomai.org skrev:
Here is my test case:
Install debian 9.6 in
In the ipipe some local_irq_enable will be replace by
enable_local_irqs, some are not。
how to determine whether it needs to be replaced ? Is there any document ?
*Linx Software Corportaion Sichuan Branch
Name：wujie duan
Tel：028-65182023-6202
E-mail: wjd...@linx-info.com
*
14 matches
Mail list logo
